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 提问,我们的支持社区将会很快回复您的疑问。

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

Default zoom not working

  • 2 个回答
  • 1 人有此问题
  • 10 次查看
  • 最后回复者为 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.