We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

為了改善您的使用體驗,本網站正在進行維護,部分功能暫時無法使用。若本站的文件無法解決您的問題,想要向社群發問的話,請到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 發問,我們的社群成員將很快會回覆您的疑問。

搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

Default zoom not working

  • 2 回覆
  • 1 有這個問題
  • 1 次檢視
  • 最近回覆由 rcastro88

more options

I am using the current version of Waterfox G3.2.0. No matter what I set my default zoom to in preferences, every tab I open defaults to a previous value I had set for the default zoom. I have only set the default zoom once which was the previous time @ 150%. Now every tab opens @ 150%. I have tried closing all tabs and then settings a new value in preferences and then opening a first tab which didn't work.

I am using the current version of Waterfox G3.2.0. No matter what I set my default zoom to in preferences, every tab I open defaults to a previous value I had set for the default zoom. I have only set the default zoom once which was the previous time @ 150%. Now every tab opens @ 150%. I have tried closing all tabs and then settings a new value in preferences and then opening a first tab which didn't work.

所有回覆 (2)

more options

The following comment is for Firefox, and may or may not apply to Waterfox.

I don't think changing the default zoom level overrides previously saved site-specific zoom levels. So for example, if you zoomed a site to 120%, that should still apply even if the default changes from 100% to 150%. But I confess I haven't played with that setting for a long time now.

There probably is a way to flush site-specific zoom levels from previous sessions, but the one that comes to mind also might flush site-specific permissions, which could be annoying...

more options

I have already changed the 'browser.zoom.siteSpecific' to false and also set 'privacy.resistFingerprinting' to false and have repeated the close all tabs cycle with no success in fixing this issue.