"We're having trouble finding that site" error page use the to-be-loaded page's custom zoom level instead of Firefox's default zoom level
Categories
(Firefox :: Tabbed Browser, defect)
Tracking
()
Accessibility Severity | s3 |
People
(Reporter: cpeterson, Unassigned)
References
Details
Attachments
(1 file)
628.18 KB,
image/png
|
Details |
Steps to reproduce
- Load https://example.com in a tab.
- Increase example.com's page zoom level to (say) 200%. I'm using the
Cmd
++
keyboard shortcut on macOS. - In another tab, load https://example.net.
- Decrease example.net's page zoom level to (say) 50%. I'm using the
Cmd
+-
keyboard shortcut on macOS. - Turn off your computer's internet connection.
- Force reload the example.com and example.net pages. I'm using the
Cmd
+Shift
+R
keyboard shortcut on macOS.
Expected result
The "We're having trouble finding that site" error page should use Firefox's default zoom level.
Actual result
The "We're having trouble finding that site" error pages use the to-be-loaded pages' custom zoom levels. In my case, example.com's error page is zoomed 200% and example.net's error page is zoomed 50%. See the attached screenshots.
This behavior is not a regression. I can reproduce in ESR 115, Firefox 122, and Nightly 124.
Comment 1•2 years ago
|
||
Thank you for the STRs, Chris! :)
I am not sure we need to overwrite user's page zoom settings since many users with low vision, users of larger screens may prefer to have specific zoom level set across their tabs, which would include the about pages, about:neterror too.
:morgan, wdyt?
Comment 2•2 years ago
|
||
Ah this might have to do with the same issue we're seeing in bug 1602235
Comment 3•2 years ago
|
||
Triaging to tabbed browser since that's where FullZoom lives, which I think controls this (though it sounds like an issue with reading from the pref store that keeps the site-specific zoom level, and that might be a separate component.)
Updated•2 years ago
|
Updated•1 years ago
|
Updated•1 years ago
|
Description
•