Steps to reproduce
Using Windows 10 version 11.296.15063.0 (Creator’s Update)
- Go to http://pdftron.s3.amazonaws.com/custom/ID-zJWLuhTffd3c/microsoft/WebViewerIE11Bug/lib/html5/ReaderControl.html#a=1&filepicker=1&pdf=ems&d=http://pdftron.s3.amazonaws.com/downloads/downloadertest/PDFReferenceLinearized.pdf
- Refresh until you see Initializing… for around 10 seconds. (if it changes to Initializing…100% or the viewer loads the problem has not been reproduced and you will need to refresh again.)
Expected Behaviour: The site and viewer should load completely each time the page is loaded.
What Happens Instead: The site gets stuck in the initialization phase.
The cause is that the XMLHttpRequest for PDFNetC.js.mem completes (according to the network tab and yet does not call the load event listener.
This build includes debugging code which validates the assumptions above. PDFNetC.js (loaded in the Web Worker) contains code which will trigger an alert after 20 seconds containing debugging statements. Note that from these statements the load event listener is simply not called when the page fails to load properly. Specifically “XHR Req; loaded PDFNetC;” should show in the alert if the bug was reproduced.
This appears to be a regression in IE11 as this did not occur in the past and we already have a number of customer reports about this issue. The problem is also reproducible in Edge 14. (before the Creator’s update)
Note that you may need to restart IE if it begins to error on refreshing.
Comments and activity
- Microsoft Edge Team
Changed Assigned To to “Steven K.”
Thank you for the submission. I believe you mentioned this does not happen in the current version of Edge? We are not presently working on feature bugs in Internet Explorer outside of security-related issues, i.e., this site is for Edge issues. If you do require Internet Explorer support, we recommend you contact Microsoft support options for business.
You can visit https://support.microsoft.com/en-us/gp/support-options-for-business and open a support incident and work with our support team to address this IE issue.
The MS Edge Team