Aug 18 2020 05:44 PM
Aug 18 2020 05:44 PM
We recently deployed Edge to our organization, and while most things are working great, we noticed some strange behavior that got introduced in v84 when Edge gained the ability to remember a user's zoom preference on IE Mode sites.
We have several web apps we run in IE Mode that use an onclick window.open to display a PDF in a new popup window. Here is an example that would (hopefully) allow you to duplicate the issue:
Aug 31 2020 04:01 PM
Here is a log showing the zoom changing without user interaction. The redacted URLs are both the same, but it seems like Edge is correctly reading the 100% zoom preference, then pulling 80% out of nowhere.
System used has 3 displays. 2 at 1440p w/ 100% scaling and 1 1080p at 125% scaling. The zoom changes on the 1080p display. I believe it is possible to duplicate on any display scaling other than 100%.
[17692:17376:0831/153523.492:VERBOSE1:dual_engine_tab_helper_win.cc(250)] CheckInternetExplorerNavigationEntry URL matches IE11 or NEUTRAL rule on sitelist: [REDACTED]
[17692:17376:0831/153523.492:VERBOSE1:internet_explorer_tab_host_win.cc(661)] SetZoom zoom_percent = 100
[17692:17376:0831/153523.493:VERBOSE1:internet_explorer_tab_host_win.cc(1076)] OnDocumentModeSet document_mode = 110000
[17692:17376:0831/153523.493:VERBOSE1:internet_explorer_tab_host_win.cc(1261)] OnHasBeforeUnloadChanged has_before_unload = 0
[17692:17376:0831/153523.513:VERBOSE1:internet_explorer_focus_watcher_win.cc(39)] IE focused:0000000000111006 IE window:00000000006B165E
[17692:17376:0831/153523.523:VERBOSE1:internet_explorer_tab_host_win.cc(483)] OnLoadingActivityChanged is_loading = 1
[17692:17376:0831/153523.523:VERBOSE1:internet_explorer_tab_host_win.cc(453)] OnFinishedSetFocus old focusing_ie_timer_ running = 1 browser_window = 00000000006B165E focus = 0000000000111006
[17692:17376:0831/153523.541:VERBOSE1:internet_explorer_tab_host_win.cc(511)] RequestHostWindowFocus is_focused = 1
[928:4832:0831/153523.617:VERBOSE1:network_delegate.cc(32)] NetworkDelegate::NotifyBeforeURLRequest: https://business.bing.com/api/v3/bookmarks
[928:4832:0831/153523.824:VERBOSE1:network_delegate.cc(32)] NetworkDelegate::NotifyBeforeURLRequest: https://graph.microsoft.com/v1.0/me/people?$top=1500&$select=id,displayName,jobTitle&$filter=personT...
[17692:17376:0831/153524.493:VERBOSE1:internet_explorer_tab_host_win.cc(1261)] OnHasBeforeUnloadChanged has_before_unload = 1
[17692:17376:0831/153524.499:VERBOSE1:internet_explorer_tab_host_win.cc(1063)] OnZoomChanged zoom_percent = 100
[17692:17376:0831/153524.553:VERBOSE1:internet_explorer_tab_host_win.cc(383)] InternetExplorerDidNavigate pending_nav_entry_id_ = 0
[17692:17376:0831/153524.557:VERBOSE1:dual_engine_tab_helper_win.cc(250)] CheckInternetExplorerNavigationEntry URL matches IE11 or NEUTRAL rule on sitelist: [REDACTED]
[17692:17376:0831/153524.558:VERBOSE1:internet_explorer_tab_host_win.cc(661)] SetZoom zoom_percent = 80
[17692:17376:0831/153524.571:VERBOSE1:internet_explorer_tab_host_win.cc(1076)] OnDocumentModeSet document_mode = 0
Sep 01 2020 11:49 AM
@AndrewSAIF Hi! Thanks for the detailed information! I've passed this on to our IE Mode team and will let you know if they have any updates or insights.
Oct 26 2020 08:11 AM
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
Oct 26 2020 08:36 AM
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.
Oct 26 2020 03:19 PM
@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.
Dec 16 2020 07:36 AM
@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.
Dec 16 2020 02:30 PM
Thanks for replying to the thread, @DiCieno !
I'm just following up with our developers to check on the fix and will follow up here.
Jan 06 2021 03:23 PM
Feb 03 2021 03:45 PM
@AndrewSAIF @DiCieno @chrish16805 Hi Everyone! Would you folks be able to share which OS versions are currently reproducing this specific issue? One easy way to get this information is by running winver.exe and reporting the number shown after OS Build in the dialog (e.g. 19041.746).
This information will help the team as they work on the fix. Thanks for your help!
Feb 04 2021 11:19 AM
Feb 04 2021 12:12 PM
I believe this is version agnostic. I can duplicate this on 2004 (19041.746) and 1909 (18363.1316) presently. We no longer have 1809 in our environment, but back when I originally reported this issue I could duplicate it on that build as well.
Mar 25 2021 04:01 PM
The fixes for Win10 2004 and 20H2 will be released in the coming days. Let us know if you have any questions. Thanks for your patience!
Mar 31 2021 03:54 PM
I installed the latest servicing stack update and this preview update to a test machine, and this appears to do the trick!
I'll do some more testing when this is out of preview. Thank you for the heads up on this, and thanks to the team for getting this resolved.
Mar 31 2021 04:12 PM
@AndrewSAIF Great! Thanks so much for doing some testing :)
Keep us updated if you run into any issues.
Apr 01 2021 04:54 AM
I've begun rolling the update out to select workstations for minimal testing as well. First tests look good.
Apr 01 2021 01:43 PM
@DiCieno Thanks for following up! Awesome to hear it is looking good so far