Closed
Bug 332275
Opened 19 years ago
Closed 5 years ago
Set a Default Text Size (or Page Zoom Level) in Tools > Options > Content > Default Page Size
Categories
(Firefox :: Disability Access, enhancement)
Firefox
Disability Access
Tracking
()
RESOLVED
DUPLICATE
of bug 1590485
People
(Reporter: cricketmilki, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: access, parity-chrome)
Attachments
(2 files)
(deleted),
patch
|
Details | Diff | Splinter Review | |
(deleted),
text/x-review-board-request
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1
Ability to set a default text size (for all websites)or page zoom level in firefox.
Let's say a site sets the font to be 16 and the user has asked for it to zoomed 120 % then, the text automatically become 19.2
Reproducible: Always
Comment 1•19 years ago
|
||
It is possible to set a minimum font-size in Firefox; if you also set a fixed font like Verdana or Arial, all text looks the same.
Reporter | ||
Comment 2•19 years ago
|
||
(In reply to comment #1)
> It is possible to set a minimum font-size in Firefox; if you also set a fixed
> font like Verdana or Arial, all text looks the same.
>
Yes But Unfortunately this is creating issues with Yahoo Mail and Google Pages.
Reporter | ||
Comment 3•19 years ago
|
||
Maybe this helps
https://addons.mozilla.org/addon.php?id=55
The updated version (not official) is here
http://daremis.free.fr/textzoom-1.7.0-fx.xpi
Flags: blocking1.9a1?
Flags: blocking1.8.0.3?
Flags: blocking1.8.0.2?
Flags: blocking-firefox2?
Please don't request blocking flags (which means "I think this bug is so important that the next release cannot possibly ship without it") for unconfirmed bugs / if you don't know what you're doing.
Flags: blocking1.9a1?
Flags: blocking1.8.0.3?
Flags: blocking1.8.0.2?
Flags: blocking-firefox2?
Comment 5•19 years ago
|
||
I think this is a good idea, and it is relatively easy to implement. (I've done so in a prototype extension already.) On page load, set ZoomManager.getInstance().textZoom = ___, which is the percentage zoom (100 = normal) from a stored preference.
Status: UNCONFIRMED → NEW
Ever confirmed: true
This is a very important feature. The OLPC XO has a 1200x900 framebuffer but an effective physical resolution about 800x600 in color mode. Because of this, it is very difficult to read text on every site, so there needs to be a way of specifying a default zoom for all sites.
I hacked the nosquint Firefox extension to change the fullZoom instead of textZoom, but you can even see Firefox trying to render any given site twice, once at the default 100%, and again at a higher zoom. On the slow XO, this is unacceptable.
This patch adds a "fullZoom.defaultPercent" preference which replaces the default zoom in the ZoomManager and FullZoom classes.
Comment 7•17 years ago
|
||
The backend code for this is already there, AFAIK, there is just no UI to set this at the moment.
Comment 8•17 years ago
|
||
Elmar is right. The backend code already supports this. The only thing you would need to do is have your front-end UI code set the browser.content.full-zoom global preference in the content prefs database via the nsIContentPrefService::setPref method.
However, note that bug 414636 will modify the behavior of this preference when it gets checked in. Nevertheless, it seems the new behavior will continue to satisfy the use case described in this bug, if I read it correctly.
Comment 10•16 years ago
|
||
I would also like to see a default full zoom setting in aboug:config, or similar, as per my original report in Bug 442533.
Comment 12•15 years ago
|
||
voting to add default full zoom level for new sites, i.e. 120% instead of 100%
Comment 13•13 years ago
|
||
Hey everybody,
Looking at AMO, I found the "Default Fullzoom Level" Addon, and I think this meets the requirements about the this new feature:
- https://addons.mozilla.org/en-US/firefox/addon/default-fullzoom-level/
Taking this into consideration, I think this new feature is not necessary yet.
On the other hand, having a field setting in firefox avoid the use of another addon to do something about usability that is so important!
Comment 15•13 years ago
|
||
Apparently, NoSquint continues to work with FireFox, according to its author.
Unfortunately, SeaMonkey is no longer compatible with NoSquint.
We are stuck with a per-site zoom set, which remembers site settings, but must
be set for each site on first visit. NoSquint allowed a global zoom of the
entire webpage so that wide screens could be utilized more fully, with scrolling
for the vertical content. I used a global setting of 150% and was happy with
every webpage rendered that way without exception. There needs to be a global
setting in FireFox/SeaMonkey to allow a set and forget zoom. I don't understand
the reasoning behind the site-specific feature that has no global setting...
Comment 16•13 years ago
|
||
(In reply to johnfull from comment #15)
I use Windows XPsp3 and SeaMonkey 2.0.14, simply because I need NoSquint and later versions cannot install it.
A recent MozillaZine thread on that subject is "Can SeaMonkey 2.9 include NoSquint or Equivalent?" at
http://forums.mozillazine.org/viewtopic.php?f=40&t=2462771
My initial message in that thread includes a link to an earlier thread which may (or may not) include some workarounds.
The fourth message in that thread suggests a possible workaround (for which I don't have enough programming knowledge to create). It wouldn't be as good as the original SeaMonkey NoSquint because it wouldn't remember site settings. But it would let Ctrl+Shift++ enlarge text size, and Ctrl+Shift+- reduce text size.
Comment 17•11 years ago
|
||
On SeaMonkey (recent 2.1x and later versions), I deal with the font size issue by using Prefbar (http://prefbar.tuxfamily.org/). It is designed to provide a lot of settings, but the only ones I installed are Min Font Size, Font-, Font+, and Full Page Zoom, with double separator lines || between each.
These are much less useful than the SeaMonkey 2.0z NoSquint version [ported to SeaMonkey from the Firefox version by Philip Chee, who apparently hasn't had the time to port it into SeaMonkey 2.xz (x>0) versions, and apparently no one else has the time either], but they are MUCH better than nothing.
Min Font Size has a checkbox. If checked when the user's website window font is at a desirable minimum, that website (or maybe all websites) has that minimum font size.
I have never figured out the details of how the Min Font size works when checked.
Full Page Zoom also has a check box. If checked, then holding the Ctrl key down and tapping the computer keyboard's + key enlarges the font AND the width of the window's contents (NOT the size of the window).
Holding the Ctrl key down and tapping the computer keyboard's - key shrinks the font AND the width of the window's contents (NOT the size of the window).
Alternatively, one can click on the Font+ and Font- buttons located on the Prefbar.
If Full Page Zoom is NOT checked, then the changes described above change the font size without changing the width of the window's contents.
R.N. (Roger) Folsom
Comment 18•11 years ago
|
||
Bug 892888 is about the same topic. One of these reports should be marked as a duplicate of the other.
Comment 20•11 years ago
|
||
Per bug 892888, this is also relevant for high-DPI displays in general and not just within the accessibility context.
Comment 21•11 years ago
|
||
In this thread, in comment 17, on 2013-07-20, I wrote that
"On SeaMonkey (recent 2.1x and later versions), I deal with the font size issue by using Prefbar (http://prefbar.tuxfamily.org/). It [has] . . . a lot of settings, but the only ones I installed are Min Font Size, Font-, Font+, and Full Page Zoom, with double separator lines || between each. . . .
"[PrefBar's] Min Font Size has a checkbox. If checked when the user's website window font is at a desirable minimum, that website (or maybe all websites) has that minimum font size.
"I have never figured out the details of how the Min Font size works when checked."
Since a NoSquint version installable on SeaMonkey 2.25 apparently still does not exist (my recollection is that the last version ported to SeaMonkey by Philip Chee was for SeaMonkey 2.0.x), I am sorry that no one has explained here how the PrefBar's Min Font size works.
R.N. (Roger) Folsom
Comment 22•7 years ago
|
||
With known addons that provide this feature going away in 57 (as far as we know), it is a good time to reconsider this as a primary option in Firefox.
@ehsan> davidb, https://bugzilla.mozilla.org/show_bug.cgi?id=332275
<@ehsan> davidb, botond and I were talking today about how that may need to be an exposed setting in our Options UI perhaps
<@ehsan> davidb, I personally have some vision issues and find it more difficult than most people to read text on pages, I'd love if my browser let me control the zoom globally...
<davidb> I like it.
<davidb> shorlander: ^
<@ehsan> davidb, botond uses an extension for this... which will stop working in 57 :(
davidb> let me see what i can do
<@ehsan> davidb, thanks :)
<davidb> you bet
Shorlander, Peter, if we get a patch could we take a feature that adds UI for this in 57?
NI Gijs, Yura for awareness.
Flags: needinfo?(yzenevich)
Flags: needinfo?(shorlander)
Flags: needinfo?(pdolanjski)
Flags: needinfo?(gijskruitbosch+bugs)
Comment 23•7 years ago
|
||
Is this a matter of exposing the browser.zoom.siteSpecific pref?
Comment 24•7 years ago
|
||
(In reply to David Bolter [:davidb] from comment #23)
> Is this a matter of exposing the browser.zoom.siteSpecific pref?
Based on this description, I doubt it:
https://searchfox.org/mozilla-central/rev/30a47c4339bd397b937abdb2305f99d3bb537ba6/browser/app/profile/firefox.js#978
Seems like this would be a popular and useful feature - Tracking this since if we want to ship it for 57 we might want some extra testing.
status-firefox57:
--- → affected
tracking-firefox57:
--- → +
Comment 26•7 years ago
|
||
This should definitely be part of FF to aid people with vision disabilities.
Comment 27•7 years ago
|
||
(In reply to :Ehsan Akhgari (needinfo please, extremely long backlog, Away Aug 7-8) from comment #24)
> (In reply to David Bolter [:davidb] from comment #23)
> > Is this a matter of exposing the browser.zoom.siteSpecific pref?
>
> Based on this description, I doubt it:
>
> https://searchfox.org/mozilla-central/rev/
> 30a47c4339bd397b937abdb2305f99d3bb537ba6/browser/app/profile/firefox.js#978
I don't really understand. My understanding from Ehsan's comment is that Ehsan wants 1 zoom factor that applies to all web pages. My understanding is that that is what that pref does if you set it to false. Ehsan/David, what am I missing?
For reference, bug 1337187 covers implementing a zoom that works per-tab rather than per-origin (which is the current default) or global (which is what happens if you flip that pref to false).
Flags: needinfo?(gijskruitbosch+bugs)
Flags: needinfo?(ehsan)
Flags: needinfo?(dbolter)
Comment 28•7 years ago
|
||
(In reply to :Gijs from comment #27)
> (In reply to :Ehsan Akhgari (needinfo please, extremely long backlog, Away
> I don't really understand. My understanding from Ehsan's comment is that
> Ehsan wants 1 zoom factor that applies to all web pages.
Yes.
> My understanding is
> that that is what that pref does if you set it to false. Ehsan/David, what
> am I missing?
I don't know if false means store globally, or don't store anything at all. In my testing it seems the latter.
Would it be easy enough to have something like browser.zoom.globalDefault nnn?
Flags: needinfo?(gijskruitbosch+bugs)
Flags: needinfo?(ehsan)
Flags: needinfo?(dbolter)
Comment 29•7 years ago
|
||
(In reply to David Bolter [:davidb] from comment #28)
> (In reply to :Gijs from comment #27)
> > My understanding is
> > that that is what that pref does if you set it to false. Ehsan/David, what
> > am I missing?
>
> I don't know if false means store globally, or don't store anything at all.
> In my testing it seems the latter.
>
> Would it be easy enough to have something like browser.zoom.globalDefault
> nnn?
I don't know. In theory, yes, the zoom code could just update (and listen for changes in) the global pref instead of the site specific one. Actually doing the zoom is managed in the docshell part of things. Maybe Manish has a more precise idea, based on bug 1358688.
Flags: needinfo?(gijskruitbosch+bugs) → needinfo?(manishearth)
Comment 30•7 years ago
|
||
> Maybe Manish has a more precise idea
Not particularly, I never had to touch or look at the pref/docshell code. The zoom code triggers restyles on the root whenever prefs are updated, and the style code knows where to find the zoom ratio (stashed on the prescontext).
Flags: needinfo?(manishearth)
Comment 31•7 years ago
|
||
(In reply to David Bolter [:davidb] (NeedInfo me for attention) from comment #22)
> Shorlander, Peter, if we get a patch could we take a feature that adds UI
> for this in 57?
Really comes down to the risk, but it would be good to figure out an approach even if it didn't make v57.
Flags: needinfo?(pdolanjski)
Comment 32•7 years ago
|
||
(In reply to Myk Melez [:myk] [@mykmelez] from comment #8)
> Elmar is right. The backend code already supports this. The only thing you
> would need to do is have your front-end UI code set the
> browser.content.full-zoom global preference in the content prefs database
> via the nsIContentPrefService::setPref method.
Firefox could provide a control to manage the global default value of that preference, for example, a select control with zoom levels from toolkit.zoomManager.zoomValues (or perhaps known safe values make more sense), starting at a default value of 100%.
For example, suppose the user selects the global default value of 120% (1.2).
With site-specific zoom: This would be the starting point for sites that do not have a site-specific preference. If the user enlarges by one step on a site, the site-specific value would be 133% (1.33), and if they reduce by a notch, the site-specific value would be 110% (1.1) (or whatever is specified by toolkit.zoomManager.zoomValues). If the user later changed the global default value, site-specific preference values do not need to change.
With tab-only zoom (siteSpecific pref'd off): The global default value would be the starting point for new tabs.
Does that make sense?
No one assigned here, and we're mid-beta for 57. Wontfix for 57 but we could still take a patch in 58.
status-firefox58:
--- → affected
Comment 34•7 years ago
|
||
I figured I post my request here instead of opening up a new report. My OS DPI is 120 (125%). I find that many new web sites I visit, where I haven't defined a per site zoom level, have text and or graphics that are too small for me to read comfortably even at 125%. These sites are ones that I don't use regularly so I wouldn't create a site specific zoom for them.
What I would like, and I'm sure others would too, is the ability via a pref to set a default zoom level for those sites that don't already have a site specific zoom level defined.
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:58.0) Gecko/20100101 Firefox/58.0
Comment 35•7 years ago
|
||
With FF 57, older add-ons that would enable setting up the zoom level globally no longer work (see this bug for an example: https://bugzilla.mozilla.org/show_bug.cgi?id=1373607).
As such, FF has become really painful to use on my HiDPI monitor. I know this feature request has only been open for 12 years ;-) so now would seem like the perfect time to implement it!
Comment 36•7 years ago
|
||
workaround |
(In reply to sxc731 from comment #35)
> With FF 57, older add-ons that would enable setting up the zoom level
> globally no longer work (see this bug for an example:
> https://bugzilla.mozilla.org/show_bug.cgi?id=1373607).
FWIW, this addon is working well for me: https://addons.mozilla.org/en-US/firefox/addon/zoom-page-we/
Comment 37•7 years ago
|
||
(In reply to Botond Ballo [:botond] from comment #36)
> (In reply to sxc731 from comment #35)
> > With FF 57, older add-ons that would enable setting up the zoom level
> > globally no longer work (see this bug for an example:
> > https://bugzilla.mozilla.org/show_bug.cgi?id=1373607).
>
> FWIW, this addon is working well for me:
> https://addons.mozilla.org/en-US/firefox/addon/zoom-page-we/
We shouldn't have to install an addon to change the default zoom, it's included in all major browsers except Firefox.
Comment 38•7 years ago
|
||
(In reply to Johannes Seldevall from comment #37)
> We shouldn't have to install an addon to change the default zoom, it's
> included in all major browsers except Firefox.
I agree. I wasn't arguing that we shouldn't implement this in Firefox, I was just pointing people to a way they can work around it in the meantime.
Comment 39•7 years ago
|
||
(In reply to Botond Ballo [:botond] from comment #36)
> FWIW, this addon is working well for me:
> https://addons.mozilla.org/en-US/firefox/addon/zoom-page-we/
Thanks for this. Yes it seems to do the job, if with a little fiddle: I find I have to click the "auto" button quite frequently (two clicks in the toolbar, rather distracting). The extension I used to depend on daily: https://addons.mozilla.org/en-US/firefox/addon/fxdpi/ was a single click for all tabs, which was very handy when switching between a hiDPI and regular monitor (laptop/desktop screen). I suspect this is a frequent enough use-case these days and since FF seems intent on capturing back market share, it would be a great idea to support it natively, without having to rely on add-ons IMHO.
I suppose the ideal way for FF to be supporting hiDPI use-cases would be for it to honour the per-display scaling factor set in the desktop environment. It currently only seems to do this with the chrome (albeit after a restart) not with the actual page content, although it's perfectly capable of scaling them...
Comment 40•7 years ago
|
||
(In reply to sxc731 from comment #35)
> With FF 57, older add-ons that would enable setting up the zoom level
> globally no longer work (see this bug for an example:
> https://bugzilla.mozilla.org/show_bug.cgi?id=1373607).
>
> As such, FF has become really painful to use on my HiDPI monitor. I know
> this feature request has only been open for 12 years ;-) so now would seem
> like the perfect time to implement it!
This isn't a good way to deal with high DPI monitors. The browser chrome isn't scaled. This feature request seems to me to be for a global option similar to layout.css.devPixelsPerPx, so what improvement does it have over that setting in the context of high DPI?
Comment 41•7 years ago
|
||
layout.css.devPixelsPerPx is global, which means it doesn't work very well in mixed-DPI situations where different displays may need quite different scale factors. By default, Firefox should respect per-monitor DPI settings (at least on macOS and Windows; I don't recall quite what the state of things is on Linux); and a Default Zoom Level setting would presumably be relative to that, so it would scale content proportionately on each monitor.
Comment 42•7 years ago
|
||
(In reply to Jonathan Kew (:jfkthame) from comment #41)
> layout.css.devPixelsPerPx is global, which means it doesn't work very well
> in mixed-DPI situations where different displays may need quite different
> scale factors. By default, Firefox should respect per-monitor DPI settings
> (at least on macOS and Windows; I don't recall quite what the state of
> things is on Linux); and a Default Zoom Level setting would presumably be
> relative to that, so it would scale content proportionately on each monitor.
Ah, I see what you mean. To be clear:
- layout.css.devPixelsPerPx overwites any OS-derived or display-specific scaling values and scale everything globally.
- this setting would apply in addition to OS-derived or display-specific scaling, but not overwrite it, which means the final derived pixels per px or each frame could be different.
Comment 43•7 years ago
|
||
I'll add my voice to indicate I'd love to have this feature as well. I'm a regular user of Firefox on a multi-monitor setup, where I'll work on one window for a while. I was a regular user of this plugin:
https://github.com/saikocat/firefox-fontdpi
which gave me a one-click ability to change the effective zoom level everywhere.
Comment 44•7 years ago
|
||
The lack of a global default zoom setting is what's blocking me from switching to Firefox Quantum. Unfortunately I couldn't find any addon to make this work either - none of the typical recommendations are compatible with Quantum, and the only one that is (ZoomPage WE) cannot set up a _global_ default, only a _per-site_ one.
I'm using a 3K monitor at native resolution with DPI set to 150 in Windows. Firefox's default zoom is just too small, I need 150% zoom for pages to be legible. Every other major browser can do this. 3K/4K displays are now fairly widespread on laptops and desktop monitors, so I think the number of users impacted is increasing daily.
Comment 45•7 years ago
|
||
(In reply to balint.farkas from comment #44)
> The lack of a global default zoom setting is what's blocking me from
> switching to Firefox Quantum. Unfortunately I couldn't find any addon to
> make this work either - none of the typical recommendations are compatible
> with Quantum, and the only one that is (ZoomPage WE) cannot set up a
> _global_ default, only a _per-site_ one.
I was able to set a global default zoom with ZoomPage WE. In the addon preferences, on the second tab ("Zoom Levels & Font Size"), under "Default Levels (%)" I set "Full" to the desired default.
Comment 46•7 years ago
|
||
(In reply to Botond Ballo [:botond] from comment #45)
> (In reply to balint.farkas from comment #44)
> > The lack of a global default zoom setting is what's blocking me from
> > switching to Firefox Quantum. Unfortunately I couldn't find any addon to
> > make this work either - none of the typical recommendations are compatible
> > with Quantum, and the only one that is (ZoomPage WE) cannot set up a
> > _global_ default, only a _per-site_ one.
>
> I was able to set a global default zoom with ZoomPage WE. In the addon
> preferences, on the second tab ("Zoom Levels & Font Size"), under "Default
> Levels (%)" I set "Full" to the desired default.
Thanks. In the meantime I managed to do the same using the NoSquint Plus extension (https://addons.mozilla.org/en-US/firefox/addon/nosquint-plus/), and made the full switch to Firefox Quantum on Windows and Android. Awesome browser :)
Sorry for polluting the bug thread.
Comment 47•7 years ago
|
||
(In reply to balint.farkas from comment #46)
> Thanks. In the meantime I managed to do the same using the NoSquint Plus
> extension (https://addons.mozilla.org/en-US/firefox/addon/nosquint-plus/),
> and made the full switch to Firefox Quantum on Windows and Android. Awesome
> browser :)
Many thanks to balint.farkas; NoSquint Plus does a great job of this. (ZoomPage WE works as well, but requires an extra step of rezooming-to-default each page afterwards.)
Further apologies for polluting the bug thread; hopefully this will help others like me who land here.
Comment hidden (mozreview-request) |
Comment 49•7 years ago
|
||
Thanks for posting a patch, SeriogaM!
Note that to get it reviewed you need to specify a reviewer in MozReview (and then publish the updated review request). Based on who reviewed previous changes to the files being modified, I think Mark Banner ("standard8") or Dão Gottwald ("dao") may be suitable reviewers.
Attachment #8932531 -
Flags: review?(standard8)
Comment 50•7 years ago
|
||
(In reply to Botond Ballo [:botond] from comment #49)
> Thanks for posting a patch, SeriogaM!
>
> Note that to get it reviewed you need to specify a reviewer in MozReview
> (and then publish the updated review request). Based on who reviewed
> previous changes to the files being modified, I think Mark Banner
> ("standard8") or Dão Gottwald ("dao") may be suitable reviewers.
Thanks. Done and done...
Updated•7 years ago
|
Attachment #8932531 -
Flags: review?(standard8) → review?(dao+bmo)
Comment 51•7 years ago
|
||
mozreview-review |
Comment on attachment 8932531 [details]
Bug 332275 - Let user set (Default) Zoom - Initial commit for review purposes.
https://reviewboard.mozilla.org/r/203584/#review209724
Thanks for looking into this but this should probably be implemented at a lower level in Gecko rather than in browser-fullZoom.js.
Attachment #8932531 -
Flags: review?(dao+bmo)
Comment 52•7 years ago
|
||
workaround |
OK.
Just in case if someone else is tired of hitting Ctrl++ on every new website - here is a simple workaround:
1. Open Browser Console
(https://developer.mozilla.org/en-US/docs/Tools/Browser_Console#Opening_the_Browser_Console)
2. On the command line (https://developer.mozilla.org/en-US/docs/Tools/Browser_Console#Browser_Console_command_line):
To Set Global Zoom (put whatever you want instead of 1.33) enter:
FullZoom._cps2.setGlobal(FullZoom.name,1.33,gBrowser.selectedBrowser.loadContext);
To Reset (back to 1) enter:
FullZoom._cps2.removeGlobal(FullZoom.name,gBrowser.selectedBrowser.loadContext);
Comment 53•7 years ago
|
||
(In reply to SeriogaM from comment #52)
> OK.
>
> Just in case if someone else is tired of hitting Ctrl++ on every new website
> - here is a simple workaround:
>
> 1. Open Browser Console
> (https://developer.mozilla.org/en-US/docs/Tools/
> Browser_Console#Opening_the_Browser_Console)
> 2. On the command line
> (https://developer.mozilla.org/en-US/docs/Tools/
> Browser_Console#Browser_Console_command_line):
>
> To Set Global Zoom (put whatever you want instead of 1.33) enter:
> FullZoom._cps2.setGlobal(FullZoom.name,1.33,gBrowser.selectedBrowser.
> loadContext);
>
> To Reset (back to 1) enter:
> FullZoom._cps2.removeGlobal(FullZoom.name,gBrowser.selectedBrowser.
> loadContext);
I'm getting "undefined", is this for Firefox Nightly only?
Comment 54•7 years ago
|
||
(In reply to Johannes Seldevall from comment #53)
> (In reply to SeriogaM from comment #52)
> > OK.
> >
> > Just in case if someone else is tired of hitting Ctrl++ on every new website
> > - here is a simple workaround:
> >
> > 1. Open Browser Console
> > (https://developer.mozilla.org/en-US/docs/Tools/
> > Browser_Console#Opening_the_Browser_Console)
> > 2. On the command line
> > (https://developer.mozilla.org/en-US/docs/Tools/
> > Browser_Console#Browser_Console_command_line):
> >
> > To Set Global Zoom (put whatever you want instead of 1.33) enter:
> > FullZoom._cps2.setGlobal(FullZoom.name,1.33,gBrowser.selectedBrowser.
> > loadContext);
> >
> > To Reset (back to 1) enter:
> > FullZoom._cps2.removeGlobal(FullZoom.name,gBrowser.selectedBrowser.
> > loadContext);
>
> I'm getting "undefined", is this for Firefox Nightly only?
No, works on regular release. The "undefined" is expected. If the default zoom does not change, try again - Up-Arrow the Enter, Ctrl+0 to test...
Comment 55•7 years ago
|
||
(In reply to SeriogaM from comment #54)
> (In reply to Johannes Seldevall from comment #53)
> > (In reply to SeriogaM from comment #52)
> > > OK.
> > >
> > > Just in case if someone else is tired of hitting Ctrl++ on every new website
> > > - here is a simple workaround:
> > >
> > > 1. Open Browser Console
> > > (https://developer.mozilla.org/en-US/docs/Tools/
> > > Browser_Console#Opening_the_Browser_Console)
> > > 2. On the command line
> > > (https://developer.mozilla.org/en-US/docs/Tools/
> > > Browser_Console#Browser_Console_command_line):
> > >
> > > To Set Global Zoom (put whatever you want instead of 1.33) enter:
> > > FullZoom._cps2.setGlobal(FullZoom.name,1.33,gBrowser.selectedBrowser.
> > > loadContext);
> > >
> > > To Reset (back to 1) enter:
> > > FullZoom._cps2.removeGlobal(FullZoom.name,gBrowser.selectedBrowser.
> > > loadContext);
> >
> > I'm getting "undefined", is this for Firefox Nightly only?
>
>
> No, works on regular release. The "undefined" is expected. If the default
> zoom does not change, try again - Up-Arrow the Enter, Ctrl+0 to test...
Works perfect, thanks.
Comment 56•7 years ago
|
||
This workaround is fabulous. Thank you!
Comment 57•7 years ago
|
||
Note that this feature will open up another way for bug 477157 to cause problems (inconsistent zooming between borders vs. other sizes, which in some cases can trigger slightly-broken-looking rendering).
(That fact shouldn't block this from proceeding IMO -- just an FYI.)
Comment 58•7 years ago
|
||
Thank you SeriogaM just what I was looking for.
I really hope this bug can be addressed (where's the vote button?), I end up using Chrome on my home (windows) laptop with a high-DPI setting. I tried fiddling with Layout.css.dpi, but that is un-usable if I move the browser window between the high-res laptop screen and standard-res external monitor.
Comment 59•6 years ago
|
||
(In reply to SeriogaM from comment #54)
> (In reply to Johannes Seldevall from comment #53)
> > (In reply to SeriogaM from comment #52)
> > > OK.
> > >
> > > Just in case if someone else is tired of hitting Ctrl++ on every new website
> > > - here is a simple workaround:
> > >
> > > 1. Open Browser Console
> > > (https://developer.mozilla.org/en-US/docs/Tools/
> > > Browser_Console#Opening_the_Browser_Console)
> > > 2. On the command line
> > > (https://developer.mozilla.org/en-US/docs/Tools/
> > > Browser_Console#Browser_Console_command_line):
> > >
> > > To Set Global Zoom (put whatever you want instead of 1.33) enter:
> > > FullZoom._cps2.setGlobal(FullZoom.name,1.33,gBrowser.selectedBrowser.
> > > loadContext);
> > >
> > > To Reset (back to 1) enter:
> > > FullZoom._cps2.removeGlobal(FullZoom.name,gBrowser.selectedBrowser.
> > > loadContext);
> >
> > I'm getting "undefined", is this for Firefox Nightly only?
>
>
> No, works on regular release. The "undefined" is expected. If the default
> zoom does not change, try again - Up-Arrow the Enter, Ctrl+0 to test...
This doesn't work with FF63.0. Setting browser.zoom.siteSpecific to false doesn't work, either.
Comment 60•6 years ago
|
||
(In reply to Dominik Mierzejewski from comment #59)
> > > > 1. Open Browser Console
> > > > (https://developer.mozilla.org/en-US/docs/Tools/
> > > > Browser_Console#Opening_the_Browser_Console)
> > > > 2. On the command line
> > > > (https://developer.mozilla.org/en-US/docs/Tools/
> > > > Browser_Console#Browser_Console_command_line):
> > > >
> > > > To Set Global Zoom (put whatever you want instead of 1.33) enter:
> > > > FullZoom._cps2.setGlobal(FullZoom.name,1.33,gBrowser.selectedBrowser.
> > > > loadContext);
> > > >
> > > > To Reset (back to 1) enter:
> > > > FullZoom._cps2.removeGlobal(FullZoom.name,gBrowser.selectedBrowser.
> > > > loadContext);
>
> This doesn't work with FF63.0. Setting browser.zoom.siteSpecific to false
> doesn't work, either.
You could try this:
Set global:
FullZoom.onContentPrefSet(null, null, 1.33);
Unset global:
FullZoom.onContentPrefRemoved(null, null, 1.33);
Note that it is contextual to the window from which you opened the Browser Console, and doesn't affect other windows as far as I can tell.
Comment 61•6 years ago
|
||
(In reply to Dominik Mierzejewski from comment #59)
> This doesn't work with FF63.0. Setting browser.zoom.siteSpecific to false
> doesn't work, either.
I just tried on FF63.0 Linux and Mac and it DOES work. Are you sure you are using the "BROWSER Console" and NOT the "WEB Console"
Comment 62•6 years ago
|
||
(In reply to Serioga from comment #61)
> (In reply to Dominik Mierzejewski from comment #59)
> > This doesn't work with FF63.0. Setting browser.zoom.siteSpecific to false
> > doesn't work, either.
>
> I just tried on FF63.0 Linux and Mac and it DOES work. Are you sure you are
> using the "BROWSER Console" and NOT the "WEB Console"
In FF63.0, the Browser Console doesn't have any field to input commands (looks like a log viewer), so yes, I did use the Web console.
Comment 63•6 years ago
|
||
(In reply to Dominik Mierzejewski from comment #59)
[...]
> Setting browser.zoom.siteSpecific to false doesn't work, either.
Correction: this kind of works, but only in a new window and for newly open tabs. Definitely not ideal, because I want to change the global zoom setting for currently open tabs when switching between standard and HIDPI screens (external monitor and 13" laptop screen, both FullHD).
Comment 64•6 years ago
|
||
(In reply to Dominik Mierzejewski from comment #62)
> (In reply to Serioga from comment #61)
> > (In reply to Dominik Mierzejewski from comment #59)
> > > This doesn't work with FF63.0. Setting browser.zoom.siteSpecific to false
> > > doesn't work, either.
> >
> > I just tried on FF63.0 Linux and Mac and it DOES work. Are you sure you are
> > using the "BROWSER Console" and NOT the "WEB Console"
>
> In FF63.0, the Browser Console doesn't have any field to input commands
> (looks like a log viewer), so yes, I did use the Web console.
You need to enable the input field by ticking "Enable browser chrome and add-on debugging toolboxes" in the devtools settings. It's not visible by default to avoid people shooting themselves in the foot.
Comment 65•6 years ago
|
||
(In reply to :Gijs (he/him) from comment #64)
> (In reply to Dominik Mierzejewski from comment #62)
[...]
> > In FF63.0, the Browser Console doesn't have any field to input commands
> > (looks like a log viewer), so yes, I did use the Web console.
>
> You need to enable the input field by ticking "Enable browser chrome and
> add-on debugging toolboxes" in the devtools settings. It's not visible by
> default to avoid people shooting themselves in the foot.
Thank you, that explains it. After enabling that setting (well hidden :>) the JS code from comment #52 does work. Well, only for new windows. It doesn't change zoom level for currently open tabs.
Updated•6 years ago
|
Keywords: parity-chrome
Comment 66•6 years ago
|
||
I think this is relevant or at least worth mentioning here: the new version of Windows 10 (1809) has a "Make text bigger" option, from Chromium bug:
"Windows 10 has "Make text bigger" in the Ease of Access center, Chrome should respect that. We have feedback directly from Microsoft that users would like Chrome text to get bigger too.
Microsoft's suggestion is that we just change the zoom percentage for the web, i.e. we make everything bigger not just the text. That ensures sites continue to reflow properly. Changing the text size only tends to cause problems beyond a few percent."
https://bugs.chromium.org/p/chromium/issues/detail?id=866513
Comment 67•6 years ago
|
||
NI'ing Asa to make sure he knows about this one. Removing other 2 year old needinfos.
Flags: needinfo?(yzenevich)
Flags: needinfo?(shorlander)
Flags: needinfo?(asa)
Updated•6 years ago
|
Flags: needinfo?(asa)
Updated•5 years ago
|
Comment 70•5 years ago
|
||
So this can finally be closed?
Comment 71•5 years ago
|
||
Yes, this was fixed in bug 1590485.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•