Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Accept non-matching document fingerprints, in PDFHistory, when the viewer is reloaded (issue 6847) #10424

Merged
merged 1 commit into from
Jan 6, 2019

Commits on Jan 6, 2019

  1. Accept non-matching document fingerprints, in PDFHistory, when the …

    …viewer is reloaded (issue 6847)
    
    This should hopefully be sufficient to address issue 6847, and given the limited impact of the code changes I'm not completely sure if this would need to be controlled by a preference!?
    
    Initially my intention was to try and provide some (slightly more detailed) implementation suggestions in the issue, but having looked briefly at doing that it would essentially have amounted to actually writing the code anyway. (Especially considering that the recent questions seemed to more-or-less ignore the information already provided in the first post.)
    
    Finally, note that since `performance.navigation.type` is marked as deprecated, a slightly different approach was choosen instead.
    Snuffleupagus committed Jan 6, 2019
    Configuration menu
    Copy the full SHA
    d467152 View commit details
    Browse the repository at this point in the history