X
Tap here to go to the mobile version of the site.
Your Firefox is out of date and may contain a security risk! Upgrade Firefox

Support Forum

This thread was closed and archived. Please ask a new question if you need help.

My websites and UI have suddenly become huge. How can I get them back to a normal, smaller size?

Posted

Yesterday all of a sudden my webpages and UI appeared to be magnified. While I can zoom out on websites, I cannot find any option to adjust the size of the UI.

I noticed that Firefox 22 (which I am running) has a new feature: "Windows: Firefox now follows display scaling options to render text larger on high-res displays". Is it possible to adjust how Firefox responds to the display scaling options perhaps?

07-27-13 - moderator locked this due to the length of this two month old thread - please post in one of the other threads discussing this issue

Modified by the-edmeister

Chosen solution

Code changes regarding HiDPI support for high resolution displays have landed in Firefox 22 and later (bug #844604).

You can modify the layout.css.devPixelsPerPx and increase or decrease the value in 0.1 or 0.05 steps to adjust the size of fonts and other elements in Firefox.

  • The layout.css.devPixelsPerPx pref is a String value parsed to a float and allows to fine tune the dimensions of all elements (user interface and web pages) more precisely (resolution 0.1 or 0.05).
  • Change the default value -1 to 1 to make it work like in previous Firefox versions (100%)

Start with a value of 1 and adjust this value with 0.1 steps or 0.05 for finer adjustments.

  • Use values between 1.0 and about 0.5 to reduce elements in size (do NOT go all the way to 0.05!)
  • Use values greater than 1.0 to magnify and make elements larger (percentage divided by DPI, % / DPI).
  • http://kb.mozillazine.org/about:config

If web pages needs to be adjusted after changing this pref then you can look at the Default FullZoom Level or NoSquint extension.

Use this extension to adjust the font size for the user interface:

Read this answer in context 5

Additional System Details

Installed Plug-ins

  • Shockwave Flash 11.7 r700
  • Google Update
  • Adobe PDF Plug-In For Firefox and Netscape 11.0.03
  • VLC media player Web Plugin 2.0.6
  • iTunes Detector Plug-in
  • McAfee MSS+ NPAPI Plugin
  • 5.1.20125.0
  • NVIDIA 3D Vision plugin for Mozilla browsers
  • NVIDIA 3D Vision Streaming plugin for Mozilla browsers
  • The QuickTime Plugin allows you to view a wide variety of multimedia content in Web pages. For more information, visit the QuickTime Web site.
  • Unity Player 3.5.6f4
  • McAfee MSC FF plugin DLL
  • Plugin for Wacom tablets.
  • Wacom Dynamic Link Library
  • NPWLPG
  • The plug-in allows you to open and edit files using Microsoft Office applications
  • Office Authorization plug-in for NPAPI browsers

Application

  • Firefox 22.0
  • User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:22.0) Gecko/20100101 Firefox/22.0
  • Support URL: http://support.mozilla.org/1/firefox/22.0/WINNT/en-GB/

Extensions

  • Adblock Plus 2.2.4 ({d10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d})
  • Add Bookmark Here ² 17.0.20121128 (abhere2@moztw.org)
  • BetterPrivacy 1.68 ({d40f5e7b-d2cf-4856-b441-cc613eeffbe3})
  • Clipboard 0.4 (clipper-prod@clipboard.com)
  • Firebug 1.11.3 (firebug@software.joehewitt.com)
  • Flagfox 4.2.8 ({1018e4d6-728f-4b20-ad56-37578a4de76b})
  • Ghostery 2.9.5 (firefox@ghostery.com)
  • Integrated Google Calendar 1.2.0 (intgcal@egarracingteam.com.ar)
  • Like.fm Social Music Tracker 1.0.13 (likefm@like.fm)
  • Microsoft .NET Framework Assistant 1.3.1 ({20a82645-c095-46ed-80e3-08825760534b})
  • Muter 0.9.8 (muter@yxl.name)
  • Pocket 3.0.1 (isreaditlater@ideashower.com)
  • Restartless Restart 9 (restartless.restart@erikvold.com)
  • Test Pilot 1.2.2 (testpilot@labs.mozilla.com)
  • Troubleshooter 1.1a (troubleshooter@mozilla.org)
  • X-notifier 3.3.1 ({37fa1426-b82d-11db-8314-0800200c9a66})
  • YSlow 3.1.4 (yslow@yahoo-inc.com)
  • Zootool 0.4 (extension@zootool.com)
  • Diigo Toolbar 5.1.0.38 ({fc2b8f80-d9a5-4f51-8076-7c7ce3c67ee3}) (Inactive)
  • feedly 14.0.482 (feedly@devhd) (Inactive)
  • Grooveshark Remote Control 0.3.3 (jid0-louF1d9B6fCB9aYNBoUJcV7HSHw@jetpack) (Inactive)

Javascript

  • incrementalGCEnabled: True

Graphics

  • adapterDescription: Intel(R) HD Graphics Family
  • adapterDescription2: NVIDIA GeForce GT 525M
  • adapterDeviceID: 0x0126
  • adapterDeviceID2: 0x0df5
  • adapterDrivers: igdumd64 igd10umd64 igd10umd64 igdumdx32 igd10umd32 igd10umd32
  • adapterDrivers2: nvd3dumx,nvwgf2umx,nvwgf2umx nvd3dum,nvwgf2um,nvwgf2um
  • adapterRAM: Unknown
  • adapterRAM2: 2048
  • adapterVendorID: 0x8086
  • adapterVendorID2: 0x10de
  • direct2DEnabled: False
  • direct2DEnabledMessage: [u'']
  • directWriteEnabled: False
  • directWriteVersion: 6.2.9200.16492
  • driverDate: 7-19-2011
  • driverDate2: 12-29-2012
  • driverVersion: 8.15.10.2455
  • driverVersion2: 9.18.13.1090
  • info: {u'AzureContentBackend': u'none', u'AzureCanvasBackend': u'skia', u'AzureFallbackCanvasBackend': u'cairo'}
  • isGPU2Active: False
  • numAcceleratedWindows: 0
  • numAcceleratedWindowsMessage: [u'']
  • numTotalWindows: 1
  • webglRenderer: Google Inc. -- ANGLE (Intel(R) HD Graphics Family)
  • windowLayerManagerType: Basic

Modified Preferences

  • accessibility.typeaheadfind.flashBar: 0
  • browser.cache.disk.capacity: 1048576
  • browser.cache.disk.smart_size.first_run: False
  • browser.cache.disk.smart_size_cached_value: 1048576
  • browser.places.smartBookmarksVersion: 4
  • browser.search.useDBForOrder: True
  • browser.startup.homepage: about:home
  • browser.startup.homepage_override.buildID: 20130514181517
  • browser.startup.homepage_override.mstone: 22.0
  • browser.tabs.warnOnClose: False
  • browser.urlbar.default.behavior: 2
  • dom.mozApps.used: True
  • dom.w3c_touch_events.expose: False
  • extensions.lastAppVersion: 22.0
  • font.internaluseonly.changed: True
  • general.useragent.extra.microsoftdotnet: ( .NET CLR 3.5.30729; .NET4.0E)
  • gfx.direct2d.disabled: True
  • gfx.direct3d.prefer_10_1: True
  • layers.acceleration.disabled: True
  • network.cookie.lifetimePolicy: 2
  • network.cookie.prefsMigrated: True
  • places.database.lastMaintenance: 1368858291
  • places.history.enabled: False
  • places.history.expiration.transient_current_max_pages: 104858
  • plugin.disable_full_page_plugin_for_types: application/pdf
  • plugin.importedState: True
  • privacy.clearOnShutdown.offlineApps: True
  • privacy.clearOnShutdown.sessions: False
  • privacy.donottrackheader.enabled: True
  • privacy.sanitize.migrateFx3Prefs: True
  • privacy.sanitize.sanitizeOnShutdown: True
  • security.warn_viewing_mixed: False
  • storage.vacuum.last.index: 1
  • storage.vacuum.last.places.sqlite: 1368369518

Misc

  • User JS: No
  • Accessibility: No
Amit Kumar Thakur 83 solutions 863 answers

Hello,

The Reset Firefox feature can fix many issues by restoring Firefox to its factory default state while saving your essential information. Note: This will cause you to lose any Extensions, Open websites, and some Preferences.

To Reset Firefox do the following:

  1. Go to Firefox > Help > Troubleshooting Information.
  2. Click the "Reset Firefox" button.
  3. Firefox will close and reset. After Firefox is done, it will show a window with the information that is imported. Click Finish.
  4. Firefox will open with all factory defaults applied.

Further information can be found in the Reset Firefox – easily fix most problems article.

Did this fix your problems? Please report back to us!

Thank you.

cor-el
  • Top 10 Contributor
  • Moderator
10751 solutions 96756 answers

Chosen Solution

Code changes regarding HiDPI support for high resolution displays have landed in Firefox 22 and later (bug #844604).

You can modify the layout.css.devPixelsPerPx and increase or decrease the value in 0.1 or 0.05 steps to adjust the size of fonts and other elements in Firefox.

  • The layout.css.devPixelsPerPx pref is a String value parsed to a float and allows to fine tune the dimensions of all elements (user interface and web pages) more precisely (resolution 0.1 or 0.05).
  • Change the default value -1 to 1 to make it work like in previous Firefox versions (100%)

Start with a value of 1 and adjust this value with 0.1 steps or 0.05 for finer adjustments.

  • Use values between 1.0 and about 0.5 to reduce elements in size (do NOT go all the way to 0.05!)
  • Use values greater than 1.0 to magnify and make elements larger (percentage divided by DPI, % / DPI).
  • http://kb.mozillazine.org/about:config

If web pages needs to be adjusted after changing this pref then you can look at the Default FullZoom Level or NoSquint extension.

Use this extension to adjust the font size for the user interface:

Modified by cor-el

Question owner

Thank you, cor-el! That was exactly what I was looking for, everything looks normal again.

MatsSvensson 0 solutions 8 answers

Helpful Reply

WARNING!!!

This is extremely bad advice! =(

I tried 0.05 and and that broke my FF 22 installation irreversibly, since all text became unreadable.


Please Note

This is explained in the next post but is not visible from all pages so I am adding it in directly

The steps have a resolution of 0.05 (0.95 0.9 0.85 0.8)

Of course you shouldn't go back all the way to 0.05 or you would have to edit the prefs.js file
A forum moderator ~J99


Then don't post "0.05" as a value, when people ask what to put in that variable. Of course people will try it. And of course nobody would expect 0.05 to be smaller than both -1 and 1, on an unknown scale.
MatsSvensson


Fortunately i could go back to version 21.

I spent a couple of hours googling this problem, and trying various workarounds, which the web is now overflowing with. But it seems impossible to completely get FF22 not looking like shit and distorting the crap out of all websites.

Now i have turned off updating, and will stick with 21 until this idiotic garbage is removed from Firefox.

And besides, even IF i could have applied some hack, SO WHAT? 99.99999% of all users wont be able to, or wont bother to do it, or wont know its even an option, which means we then have to start designing websites that both look good on non-swollen AND swollen (Firefox) browsers!

Congratulation to making FF the new IE6.

OBVI-FU**ING-OUSLY its NOT a good idea to start telling people to apply various hacks to work around this, since this will fragment the way the same sites look in the same browsers (even more so).

The correct response is to grasp that this "feature" is broken and remove it, or fix it, an stop rolling out the broken version before it does even more damage.

How the F can they roll out something THIS epically broken? I have found posts dating back months, from people using beta versions, who reported exactly this problem. And STILL it was rolled out?

Modified by MatsSvensson

cor-el
  • Top 10 Contributor
  • Moderator
10751 solutions 96756 answers

The steps have a resolution of 0.05 (0.95 0.9 0.85 0.8)
Of course you shouldn't go back all the way to 0.05 or you would have to edit the prefs.js file

john31415 0 solutions 3 answers

The modification suggested above partly fixes the problem. However it also helps to show how serious an issue this is. It affects many elements of the browser window and while the fix might restore some elements others are then found to be adversely affected such as a reduced address bar font. All of my No Squint site settings are effectively lost. Some web pages cannot now be made to fit in the width of the window by zooming out such that the horizontal scroll bar always shows.

Any help to get back to Firefox version 21 would be greatly appreciated.

jscher2000
  • Top 10 Contributor
2365 solutions 20922 answers

Hi john31415, could you try this mixed approach:

(1) Install the Theme Font & Size Changer extension and set the font to a larger size such as 17 (you can fine tune this later) to enlarge the chrome area (menu, toolbar, tab area) in advance of step 2.

(2) Set the layout.css.devPixelsPerPx preference to 1.0 to size the content and chrome to 96dpi. Hopefully this will be compatible with your saved NoSquint settings.

Mozilla discloses security flaws after each new release, so it's preferable not to downgrade if you can avoid it. If the above approach doesn't work for you, old versions are available from the downgrade part of the following article: Install an older version of Firefox. After NoSquint updates, you may want to try Firefox 22 again and see how they work together.

jscher2000
  • Top 10 Contributor
2365 solutions 20922 answers

Hi MatsSvensson, sorry to hear about your 0.05 experience. Maybe about:config needs an "undo" command?

As currently designed, the "device pixels per CSS pixel" setting governs both the content and the chrome of the browser. I think it would be better to separate them, but I haven't searched to see whether anyone has filed a request for enhancement on that. In the short run, you could consider an add-on workaround.

Whether you choose to set layout.css.devPixelsPerPx to optimize the appearance of the content or the chrome, you can use an extension to tweak the other area to your liking.

mrmojorisin27 0 solutions 2 answers

Hi, I have the same problem, how do you fix it? My FF it need to be looked with a microscope, I can't see any kind of text!

Any one have a solution for this? All my text now looks microscopic, how I can get it back, or modify the options?

Help! =(

cor-el
  • Top 10 Contributor
  • Moderator
10751 solutions 96756 answers

This sounds like a case where you should take notice f the warning to make changes to prefs.

Note that this is not a new pref (2009):

  • Bug 493202 - Add a hidden pref to control the CSS-pixel-to-dev-pixel ratio
  • Bug 674373 - [10.7] Support HiDPI mode on OS X Lion
jscher2000
  • Top 10 Contributor
2365 solutions 20922 answers

Hi mrmojorisin27, can you see the menu/toolbar/tab area? If so, try this:

(1) In a new tab, type or paste about:config in the address bar and press Enter. Click the button promising to be careful.

(2) In the filter box, type or paste pix and pause while the list is filtered

(3) Double-click layout.css.devPixelsPerPx and change its value to 1.5 (that is equivalent to 150%) and OK that. I'm sure everything will be too large at this point, but at least you can see and adjust from this point.

cor-el
  • Top 10 Contributor
  • Moderator
10751 solutions 96756 answers

Did you make changes to the layout.css.devPixelsPerPx pref?

In that case you can edit the prefs.js file and either remove the line or modify its value to 1.0 or 2.0 to increase all elements.

user_pref("layout.css.devPixelsPerPx", "2.0");
MatsSvensson 0 solutions 8 answers

Helpful Reply

Just to be clear: Im not wasting any time on any FF version that still has this bug.

As far as Im concerned, FF is boned if this isn't fixed immediately. The average user will notice that sites look completely different in FF than in other browsers, and move to chrome or IE or whatever. And then that's it.

A basic thing like this just HAS to work without the user needing to mess around with the plumbing inside walls.

For years i have recommended FF to people over IE & chrome.
No more. (And don't edit this line out again)

Modified by MatsSvensson

mrmojorisin27 0 solutions 2 answers

Thanks to all of you, problem fixed!.. FF its working again, but I must say it's the same issue, puting my value to 1.0 did not resolve the original settings, or 1.5 is way too big. I hope for a dissable option.

Thanks!

jscher2000
  • Top 10 Contributor
2365 solutions 20922 answers

Hi MatsSvensson, a better way to give feedback is Help > Submit Feedback. However, that site requires the latest version of Firefox.

Does the average user change from the Windows default DPI setting to a high DPI setting? If they do, they might appreciate no longer have to press Ctrl++ to increase the tiny text on most pages. The text of some pages will indeed be too large. For that, there is Ctrl--. I guess we're trading one inconvenience for another.

Turnerten 0 solutions 2 answers

Can I please get a way to restore my font sizes exactly the way they were prior to 22? Like, exactly how they were. What settings can make it like this? Until then I am going back to 21.

jscher2000
  • Top 10 Contributor
2365 solutions 20922 answers

Hi Turnerten, I posted a reply for you over here: https://support.mozilla.org/en-US/que.../963035#answer-449056. Does that fix it?

MatsSvensson 0 solutions 8 answers

I did that, thanks for the tip. (It seems to work fine to use the feedbackpage in FF21)

And there are plenty of people mad about the scaling: https://input.mozilla.org/en-US/

At least in Win7 & Win8 you get an upped DPI-setting automatically when you use a fairly high-rez monitor. The average user wont have to know anything about changing the dpi-settings, or even know there is such a setting anywhere.

27" monitors with 2560x1440 rez, for example, are dropping rapidly in prize, and cheap(ish) 4K ones are already arriving. So expect this problem to explode.

Modified by MatsSvensson

john31415 0 solutions 3 answers

Thanks for the information about downgrading Firefox which has fully resolved my problem.

Encouraging people to mess about with work arounds is only going to compound the frustrations of many thousands of users.

A Firefox update should be made available as soon as possible including the necessary security fixes but without the code which is known to be causing this issue.

I'll run Firefox 21 for a while but if a proper fix doesn't appear soon I'll be forced, reluctantly, to move back to IE.

Thanks also for the feedback instructions which I will make use of.

MatsSvensson 0 solutions 8 answers

Update: I have played around with setting a while, and i think its pretty clear this is a bug.

When you change the zoom/DPI setting in windows, it affects the size of things, like Firefox.

I am currently using 120% zoom on a 27" screen with 2560x1440 resolution. (125% is the default for this screen-size)

This makes the entire UI 20% larger including Firefox 21 and below. So Forefox is already magnified, along with the rest of the UI.

What the new feature/bug in FF22 does, is zooming the FF UI & content separately on top of the zoom already done.

How exactly is this " respecting the pixel density"? No other programs seem to be " respecting the pixel density" by double dipping in this way.

See attached screen-grabs for an example of how the same site looks in IE10, FF pre 22 and FF22. All browsers unchanged and set to default zoom (100%).

The site has a fluid responsive design, that adapts to the browser window size.

Window size is identical, about 1920x1200

See if you can spot the one that does things differently...

Modified by MatsSvensson