X
Tap here to go to the mobile version of the site.

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

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
jscher2000
  • Top 10 Contributor
8578 solutions 70134 answers

Hi Haterade, after further testing, I think there is a problem specific to Facebook (I only checked the home page). I only discovered this after using Ctrl+Shift+r to reload the page bypassing cached files.

If I set layout.css.devPixelsPerPx=1.0 AND use Facebook without ANY zoom, then there is no problem. However, if I use zoom and reload (Ctrl+r) or hard reload (Ctrl+Shift+r) then I get the broken layout.

This only occurs if JavaScript is enabled, so there seems to be a compatibility issue between the scripts Facebook uses to adapt itself to different window sizes and Firefox 22. Hmmm...

Hi Haterade, after further testing, I think there is a problem specific to Facebook (I only checked the home page). I only discovered this after using Ctrl+Shift+r to reload the page bypassing cached files. If I set layout.css.devPixelsPerPx=1.0 AND use Facebook without ANY zoom, then there is no problem. However, if I use zoom and reload (Ctrl+r) or hard reload (Ctrl+Shift+r) then I get the broken layout. This only occurs if JavaScript is enabled, so there seems to be a compatibility issue between the scripts Facebook uses to adapt itself to different window sizes and Firefox 22. Hmmm...
Voxed 0 solutions 1 answers

Firefox now displays like Internet Explorer in respect of scaling. (if using windows) Our Windows 7 laptop is set to display at 125%. Personally I don't like it but the other user of this laptop prefers bigger text.

I have therefore used the about:config hack detailed above but also restored my address bar text size, etc, using the "Theme Font & Size Changer" add-on.

It occurs to me that maybe a significant number people who use Firefox were using it partly because Windows scaling did not apply and web pages therefore looked better than they do in IE.

Firefox now displays like Internet Explorer in respect of scaling. (if using windows) Our Windows 7 laptop is set to display at 125%. Personally I don't like it but the other user of this laptop prefers bigger text. I have therefore used the about:config hack detailed above but also restored my address bar text size, etc, using the "Theme Font & Size Changer" add-on. It occurs to me that maybe a significant number people who use Firefox were using it partly because Windows scaling did not apply and web pages therefore looked better than they do in IE.
Zwaardbei 0 solutions 1 answers

I too have reverted to version 21 of firefox after encountering this problem. I have tried messing with layout.css.devPixelsPerPx, but this resulted in a correctly sized UI with a font that is too small, or an oversized UI with a correctly sized font. I agree with the statement that users shouldn't have to mess around in about:config if they just want to browse the internet.

I too have reverted to version 21 of firefox after encountering this problem. I have tried messing with layout.css.devPixelsPerPx, but this resulted in a correctly sized UI with a font that is too small, or an oversized UI with a correctly sized font. I agree with the statement that users shouldn't have to mess around in about:config if they just want to browse the internet.
rknetwork 0 solutions 1 answers

Why are you doing it? FF == IE5 NOW?

First some of the jQuery stopped working (in ver. 21), now this...

Roll it all back to ver. 20 and hire new developers.

edit Forum rules and guidelines ~J99.

Why are you doing it? FF == IE5 NOW? First some of the jQuery stopped working (in ver. 21), now this... Roll it all back to ver. 20 and hire new developers. <sub>edit [[Forum rules and guidelines]] ~J99</sub>.

Modified by John99

jscher2000
  • Top 10 Contributor
8578 solutions 70134 answers

Hi rknetwork, what problem do you have with jQuery in Firefox 21+? I think it would be best to start a new question on that since this one already is 5 pages long:

https://support.mozilla.org/questions/new/desktop/websites

Hi rknetwork, what problem do you have with jQuery in Firefox 21+? I think it would be best to start a new question on that since this one already is 5 pages long: https://support.mozilla.org/questions/new/desktop/websites
cyanobluegirl0308 0 solutions 1 answers

I've done this twice and it takes about an hour to reload my tools, add-ons, etc., and I'm right back where I started. Neither reset zoom or resetting FF, works to solve this problem. I am in my sixties and so came late to the digital revolution. Most the answers to this question, and, BOY am I not alone in this, are way beyond my capabilities to duplicate. I'll be frank and say up front, I don't understand one word in ten. Isn't there a bug fixing tool for this problem? I am not switching out from FF, regardless, especially given the security and privacy that larger servers don't have anymore if they ever did. I have joined the EFF and the 'stop watching me' movements, because that broad umbrella enjoyed by the NSA and others scares me a lot. Even though if they got my online communications, search history, etc. it would bore them to death, but I vehemently protest their right to do so. I support the entire Constitution and that includes the Fourth Amendment. But, this zoom problem with FF 22 is driving my crazy. If you don't have a fix, is there anyway to reload FF21? You have to have about half the big brains out there, surely you guys can come up with a 'help the old geezers fix this problem' tool. HELP! Pretty please.

I've done this twice and it takes about an hour to reload my tools, add-ons, etc., and I'm right back where I started. Neither reset zoom or resetting FF, works to solve this problem. I am in my sixties and so came late to the digital revolution. Most the answers to this question, and, BOY am I not alone in this, are way beyond my capabilities to duplicate. I'll be frank and say up front, I don't understand one word in ten. Isn't there a bug fixing tool for this problem? I am not switching out from FF, regardless, especially given the security and privacy that larger servers don't have anymore if they ever did. I have joined the EFF and the 'stop watching me' movements, because that broad umbrella enjoyed by the NSA and others scares me a lot. Even though if they got my online communications, search history, etc. it would bore them to death, but I vehemently protest their right to do so. I support the entire Constitution and that includes the Fourth Amendment. But, this zoom problem with FF 22 is driving my crazy. If you don't have a fix, is there anyway to reload FF21? You have to have about half the big brains out there, surely you guys can come up with a 'help the old geezers fix this problem' tool. HELP! Pretty please.
jscher2000
  • Top 10 Contributor
8578 solutions 70134 answers

Hi cyanobluegirl0308, you have different options depending on which parts of the enlarged Firefox display you want to adjust. For example, are the toolbar font sizes okay, but the page content too large? Everything too large?

Hi cyanobluegirl0308, you have different options depending on which parts of the enlarged Firefox display you want to adjust. For example, are the toolbar font sizes okay, but the page content too large? Everything too large?
masoud27000 0 solutions 2 answers

i have problem my website

شارژ رایتل

i have problem my website [http://www.timeup.ir شارژ رایتل]
jscher2000
  • Top 10 Contributor
8578 solutions 70134 answers

Hi masoud27000, please describe the problem in more detail.

Hi masoud27000, please describe the problem in more detail.
ewezer 0 solutions 2 answers

What's the hell of FF 22? Do you think we and other change the website to meet your new feature or just move to other browser? Do you remember the fxxking IE? It's a worst experience for the users so they move to FF/Chrome. Now you are doing the same idiot guy...

What's the hell of FF 22? Do you think we and other change the website to meet your new feature or just move to other browser? Do you remember the fxxking IE? It's a worst experience for the users so they move to FF/Chrome. Now you are doing the same idiot guy...

Modified by ewezer

mamefox 0 solutions 18 answers

Hi ewezer, your opion is correct. No one from Mozilla is interested in the situation of webdesigners or the 100% of homepage-users. Support means help. But no one here is allowed really to help, because the only solution is, to fix the well known bug in Mozilla Firefox 22 und 23 beta. Mozilla is celebrating FirefoxOS. A lot of twitter-profiles are created around FirefoxOS. But no one talks about the really problem of Mozilla: The layout-bug in Firefox Version 22. So, we have only the alternative, to attack Mozilla. We must publish the facts in our twitter- und facebook-accounts and in all our homepages. Here you find an example: http://www.praeludio.de/impressum.html#ff22. I have from all my homepages refered to this site with an examplary campaign.

Hi ewezer, your opion is correct. No one from Mozilla is interested in the situation of webdesigners or the 100% of homepage-users. Support means help. But no one here is allowed really to help, because the only solution is, to fix the well known bug in Mozilla Firefox 22 und 23 beta. Mozilla is celebrating FirefoxOS. A lot of twitter-profiles are created around FirefoxOS. But no one talks about the really problem of Mozilla: The layout-bug in Firefox Version 22. So, we have only the alternative, to attack Mozilla. We must publish the facts in our twitter- und facebook-accounts and in all our homepages. Here you find an example: http://www.praeludio.de/impressum.html#ff22. I have from all my homepages refered to this site with an examplary campaign.
jscher2000
  • Top 10 Contributor
8578 solutions 70134 answers

Hi ewezer and mamefox, I realize that some site designs will take more time to adapt to browsers that scale for High DPI displays. But I think it makes sense to start working on it now, so your sites will be prepared for:

Hi ewezer and mamefox, I realize that some site designs will take more time to adapt to browsers that scale for High DPI displays. But I think it makes sense to start working on it now, so your sites will be prepared for: * IE 11: [http://msdn.microsoft.com/en-us/library/ie/dn265030(v=vs.85).aspx High DPI support (Preliminary)] * Chrome 30: [http://news.cnet.com/8301-1023_3-57593030-93/chrome-gets-high-resolution-screen-support-on-windows-too/ Chrome gets high-resolution screen support on Windows, too | Internet & Media - CNET News]
mamefox 0 solutions 18 answers

Good morning jscher2000, thank you for your opinion. What you wrote, is very important, because it seems, that the producer of browsers brake a law while implementing a new technology through the backdoor.

2014 will HTML5 get the webstanard. No problem because this point was published long ago, discussed and it exists a lot of material, to learn the new technology of webdesign. But most important: Nobody is forced to use HTML5 because the W3C respects the law of compatibility.

But if you write, "that some site designs will take more time to adapt to browsers that scale for High DPI displays", then you mean, that with this new technology it is no compatibility guaranteed. No one has published this point. No one has this aspect discussed. So it is true, what I wrote, that Mozilla (and other organizations) ignore both webdesigner and the normal user.

My question to you: What can webdesigners do, to adapt the design of their websites to this new technology? I don't mean, how I can tune the browser. I mean the html- und css-structure behind the visible sites. And what will be with all the websites, which cannot be adapted, because the Dreamweaver-designers aren't able to do this or because it will be to much time to change the whole internet and/or because these changes are simply to expensive? Would you please now discuss these points, if Mozilla missed to discuss this at the right time?! Thank you very much!

Good morning jscher2000, thank you for your opinion. What you wrote, is very important, because it seems, that the producer of browsers brake a law while implementing a new technology through the backdoor. 2014 will HTML5 get the webstanard. No problem because this point was published long ago, discussed and it exists a lot of material, to learn the new technology of webdesign. But most important: Nobody is forced to use HTML5 because the W3C respects the law of compatibility. But if you write, "that some site designs will take more time to adapt to browsers that scale for High DPI displays", then you mean, that with this new technology it is no compatibility guaranteed. No one has published this point. No one has this aspect discussed. So it is true, what I wrote, that Mozilla (and other organizations) ignore both webdesigner and the normal user. My question to you: What can webdesigners do, to adapt the design of their websites to this new technology? I don't mean, how I can tune the browser. I mean the html- und css-structure behind the visible sites. And what will be with all the websites, which cannot be adapted, because the Dreamweaver-designers aren't able to do this or because it will be to much time to change the whole internet and/or because these changes are simply to expensive? Would you please now discuss these points, if Mozilla missed to discuss this at the right time?! Thank you very much!
jscher2000
  • Top 10 Contributor
8578 solutions 70134 answers

Hi mamefox, users will always be able to manually adjust the zoom of sites as they have always done. Some web designers will leave it at that. If you want to exercise more control, you could explore the use of media queries to specify different font sizes and related metrics, and change your CSS images. There are many articles on media queries focused on small screens, but I suspect the device pixel ratio will be attracting more attention. Here is the MDN page: CSS media queries - Web developer guide | MDN.

Hi mamefox, users will always be able to manually adjust the zoom of sites as they have always done. Some web designers will leave it at that. If you want to exercise more control, you could explore the use of media queries to specify different font sizes and related metrics, and change your CSS images. There are many articles on media queries focused on small screens, but I suspect the device pixel ratio will be attracting more attention. Here is the MDN page: [https://developer.mozilla.org/en-US/docs/Web/Guide/CSS/Media_queries CSS media queries - Web developer guide | MDN].
mamefox 0 solutions 18 answers

Hi jscher200, thank you for your answer, which is interesting. But it is not a solution of the problem. Otherwise you would have published the solution already. To influence the pixel ratio via media queries can't solve the bug in Mozillas Firefox 22. And this bug is the reason, why the websites aren't compatibel in the Browser Firefox 22. The compatibility of the existing websites can only be guaranteed without the bug in Firexfox 22. And this bug can only solve Mozilla. Or isn't the compatibility important for Mozilla?

Hi jscher200, thank you for your answer, which is interesting. But it is not a solution of the problem. Otherwise you would have published the solution already. To influence the pixel ratio via media queries can't solve the bug in Mozillas Firefox 22. And this bug is the reason, why the websites aren't compatibel in the Browser Firefox 22. The compatibility of the existing websites can only be guaranteed without the bug in Firexfox 22. And this bug can only solve Mozilla. Or isn't the compatibility important for Mozilla?
ewezer 0 solutions 2 answers

This is a interesting problem. I just want to know. If I use device with Retina display and install firefox 22, does the blur and image enlarge problem solve? If it is true, I think firefox mobile should apply this high DPI support but not firefox desktop. Most of users are using a normal LED that does not support high DPI.

This is a interesting problem. I just want to know. If I use device with Retina display and install firefox 22, does the blur and image enlarge problem solve? If it is true, I think firefox mobile should apply this high DPI support but not firefox desktop. Most of users are using a normal LED that does not support high DPI.
jscher2000
  • Top 10 Contributor
8578 solutions 70134 answers

Hi mamefox, I think your latest question is different than your earlier one. Earlier, I thought you were asking what webmasters could do to adapt their sites for Firefox 22, IE11, and Chrome 30, but your later question is how to persuade Mozilla to undo the change so webmasters do not need to change their sites. I don't have an answer for that.

Hi mamefox, I think your latest question is different than your earlier one. Earlier, I thought you were asking what webmasters could do to adapt their sites for Firefox 22, IE11, and Chrome 30, but your later question is how to persuade Mozilla to undo the change so webmasters do not need to change their sites. I don't have an answer for that.
jscher2000
  • Top 10 Contributor
8578 solutions 70134 answers

Hi ewezer, I haven't had the pleasure of using a Retina display. I wonder whether the Apple store will let me install Firefox? Hmm...

Hi ewezer, I haven't had the pleasure of using a Retina display. I wonder whether the Apple store will let me install Firefox? Hmm...
mamefox 0 solutions 18 answers

Hi jscher2000, everyone in the forum of Mozilla support under the headline 'Browser resolution has become bigger' cries for help! All websites are acceptable to all browsers apart from Firefox 22. All websites have been good-looking in Firefox 21, 20, 19, 18, ... But the websites aren't all right in Firefox 22. So there is no reason, to change the websites, but only a reason to change Firefox 22. On 6 Sites under this theme you can read this. And now you have understood, that you can't give the right answer to the people, who cry for help to the support of Mozilla. You are supporter and so you have to support the users, talking to Mozilla about the results of this forum. Fact is. that Firefox 22 isn't compatibel. The results seen in Firefox 22 aren't identical with the results in previous versions of Firefox and in other browsers. This proofs, that Firefox 22 has a bug. All the people in this forum tell you, there is a bug. Normaly you would read it, say thank you and repair the bug. What is the damned reason, that Mozilla ignores the cry for help? Why ignores Mozilla the law of compatibility?

Hi jscher2000, everyone in the forum of Mozilla support under the headline 'Browser resolution has become bigger' cries for help! All websites are acceptable to all browsers apart from Firefox 22. All websites have been good-looking in Firefox 21, 20, 19, 18, ... But the websites aren't all right in Firefox 22. So there is no reason, to change the websites, but only a reason to change Firefox 22. On 6 Sites under this theme you can read this. And now you have understood, that you can't give the right answer to the people, who cry for help to the support of Mozilla. You are supporter and so you have to support the users, talking to Mozilla about the results of this forum. Fact is. that Firefox 22 isn't compatibel. The results seen in Firefox 22 aren't identical with the results in previous versions of Firefox and in other browsers. This proofs, that Firefox 22 has a bug. All the people in this forum tell you, there is a bug. Normaly you would read it, say thank you and repair the bug. What is the damned reason, that Mozilla ignores the cry for help? Why ignores Mozilla the law of compatibility?