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

[PDFHistory] Move the IE11 pushState/replaceState work-around to src/shared/compatibility.js (PR 10461 follow-up) #11318

Merged

Conversation

Snuffleupagus
Copy link
Collaborator

I've always disliked the solution in PR #10461, since it required changes to the PDFHistory code itself to deal with a bug in IE11.
Now that IE11 support is limited, it seems reasonable to remove these pushState/replaceState hacks from the main code-base and simply use polyfills instead.

…`src/shared/compatibility.js` (PR 10461 follow-up)

I've always disliked the solution in PR 10461, since it required changes to the `PDFHistory` code itself to deal with a bug in IE11.
Now that IE11 support is limited, it seems reasonable to remove these `pushState`/`replaceState` hacks from the main code-base and simply use polyfills instead.
@Snuffleupagus
Copy link
Collaborator Author

/botio-linux preview

@pdfjsbot
Copy link

From: Bot.io (Linux m4)


Received

Command cmd_preview from @Snuffleupagus received. Current queue size: 0

Live output at: http://54.67.70.0:8877/e8b56c6b4772851/output.txt

@pdfjsbot
Copy link

From: Bot.io (Linux m4)


Success

Full output at http://54.67.70.0:8877/e8b56c6b4772851/output.txt

Total script time: 1.69 mins

Published

@timvandermeij timvandermeij merged commit 3a05f6f into mozilla:master Nov 11, 2019
@timvandermeij
Copy link
Contributor

Looks much better this way. The more we can isolate browser-specific hacks, the better.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants