Forum Discussion
Possible IE Mode bug - window.open with pdf target causes Edge to adjust zoom
We have the exact same issue, been banging our heads the past few days trying to track the cause down.
We can replicate the issue.
We found the issue on a 4k laptop and screen. Loading one of our web apps in IE Mode clicking on a pdf opens in new tab, go back to the web app tab and it zooms out. We've found if you also set the Windows display properties dpi to another value such as 125% on a 1920x1080 screen when you load the pdf it zooms out to 80%, then because the web app is on the same domain as the pdf when going back to the web app its zoomed out to 80% also.
If I set the dpi zoom to 150% on a 1920x1080 resolution screen and load the pdf it zooms out to 67%. At first we thought it was the Adobe settings zooming out to page width, but I've set Adobe zoom to 10% and reloaded the pdf in IE Mode and that appears tiny at 10% but Edge still zooms out for some reason.
We would use the Edge Chromium built in pdf viewer but layers don't show, so have to use IE Mode so it loads the Adobe viewer instead.
We are currently using 86.0.622.51 but I've also tried dev build 88.0.673.0
We have found two workarounds for now but not ideal. Add the switches to the program shortcut to stop it using the 125% or 150% dpi scaling setting in Windows and use 100% natively.
- Kelly_YOct 26, 2020Microsoft
chrish16805 AndrewSAIF Hi! Thank you both for the information! Just to give a quick update, our team has investigated and they are currently working on a fix. There is no firm ETA quite yet for the fix. We need to work with the Windows team on this so it might take a little longer but we'll be sure to follow up here with updates.
-Kelly
- DiCienoDec 16, 2020Copper Contributor
Kelly_Y AndrewSAIF chrish16805 I'm so glad you've done the investigative work already, so THANK YOU very much. I just ran into this problem for our users and this thread popped on an easy search. I'd love to finally retire IE (native at least) from our workstations and this looks like the last hurdle. Seeing as how it's already official logged and in the Edge pipeline I can at least affirm to my disgruntled users that a fix will likely happen in the future.