Hi marv6, how far off was the zooming in Firefox 22? Let's say hypothetically that you regularly wanted to reduce the zoom by two adjustments (Ctrl- twice). You can use one of these extensions and set the default or global zoom level to about 80% to adjust all pages to that size.

• Default FullZoom Level
• NoSquint (use global setting)

Then you would manually increase or decrease zoom on other pages where your new default setting isn't quite right.

I'd like to mention that the combination of changing the layout.css.devPixelsPerPx to 1.0 and installing the Theme & Font Size changer add-on is working well for me.

The responsive design tool works properly again (it didn't scale correctly before the above fix).

The only thing I've noticed that's not working as before: No Squint no longer seems to remember the zoom settings for various sites. Whatever I use for one page is the same for any other page I go to afterwards (same window/tab or new one). Anyone else find this? It's a bit annoying...

You can set the layout.css.devPixelsPerPx pref on the about:config page to 1.0 (current default value is -1.0) to restore the behavior of previous Firefox versions.
If you need to adjust the dimensions of icons on toolbars the adjust the value of this pref in steps of 0.1 or 0.05 starting with 1.0.

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

• Theme Font & Size Changer: https://addons.mozilla.org/firefox/addon/theme-font-size-changer/

You can look at the Default FullZoom Level or NoScript extension if web pages need to be adjusted after changing the layout.css.devPixelsPerPx pref.

• Default FullZoom Level: https://addons.mozilla.org/firefox/addon/default-fullzoom-level/
• NoSquint: https://addons.mozilla.org/firefox/addon/nosquint/

• https://support.mozilla.org/kb/forum-response-Zoom-feature-on-Firefox-22

Thanks for all of your helpful comments. My concern remains is that I did not have to make any of these adjustments in ver. 21.0. Why is it now necessary to make these adjustments in ver 22.0 ? This creates additional work in order to get the text and page size to the level of the previous version. I tried re-setting to 1.0 in 22 and it helps with some things, but, the size of my web mail in earthlink is still somewhat off and in facebook it is even worse. Did not have these problems with Firefox 21.0 at all. I will keep trying to get this to work and will try some of your suggestions, but, this should not be necessary. Is Firefox leaving the desktops and laptops behind to get it to work in newer devices?

Hi marv6, I think work on this feature started when Apple launched the high density "Retina" screen on its MacBook laptops. It has taken a long time to come to fruition and only too effect for Windows users in Firefox 22.

Edit: per cor-el's link below, this work dates back to at least 2008.

I suspected as much. Try to make it better for others at our expense. Hope Firefox will try to reach a happy medium on this problem. There still must be a lot of desktop users out there, who are negatively affected by Firefox 22.0.

• https://bugzilla.mozilla.org/show_bug.cgi?id=394103#c53

Hi marv6, this isn't meant to be at anyone's "expense." If you set your Windows DPI scaling to something larger than 100%, Firefox views this as a cue that you want larger text. If that signal is not correct, you can change Firefox's behavior. It's harder to do that than it has to be, those are the settings and workarounds we have today. To give input on new features for the future, I suggest using Help > Submit Feedback.

Thanks for the info. The link above is too technical for me to even begin to understand. Please explain my Windows DPI scaling? Why are all of these fixes and patches necessary with 22.0, but, were not necessary with 21.0 and earlier versions. Also, version 22.0 is still not compatible with Norton Vulernability Protection. Is Firefox getting even too complex for Norton? Have been a long time user of Netscape and Firefox, but it is getting too complicated for an old man like me.

The DPI issue was a known issue for sometime, but it took awhile to get a fix in, which is why it respects your DPI settings in 22 but not 21 (updates fix bugs, a bug was fixed in 22). The norton issue should be fixed now, run your live updater in norton. Norton had a fail and didn't get their software updated in time for our well known and publicly visible release schedule.

I have a w22 screen and until Firefox 22 there was no DPI issue on my computer. Now there is an issue. I can reduce my Windows DPI setting back to 96, which may help in Firefox, but, it will then make everything else smaller.

All you need to do is the following:

 There's more than one way to resolve this problem.   See the Webpages are large and blurry after updating Firefox - how to fix  article for one suggestion.   Here's  another possible solution:

• Type about:config into the Firefox address bar and tap on the Enter key.
• If the warning This might void your warranty appears, click I'll be careful, I promise.
• Search for layout.css.devPixelsPerPx

• Double-click on layout.css.devPixelsPerPx to modify its value. The default is -1.0 in Firefox 22 and above. Change it to 1.0 to make it work like in previous Firefox versions.

If necessary, further adjust the value in 0.1 or 0.05 steps. Use values between 1.0 and about 0.5 to reduce elements in size. Use values greater than 1.0 to increase size. For example, a value of 1.25 will increase font size to 125% to accommodate the default DPI setting in Windows 8. Double check the value that you enter. Setting a too small value will make everything disappear and a too large value will blow things up.

If web pages still need to be adjusted then you can look at the Default FullZoom Level or NoSquint extension.

To adjust the font size for the user interface, you can use the Theme Font & Size Changer extension.

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

Thank you.

Hi marv6, I don't think that bug report link was meant for you.

The rest of this is obsolete based on the above discussion

Your Windows display settings let you set your font size in steps: 100%, 125%, 150% and so forth. But it sets more than that. It also affects desktop icons, the Start menu, and nearly all application menus and toolbars.

You can see your setting using the "Display" control panel from the Start menu if you're curious.

Thanks for your help. For now I am back to using Firefox 21.0. Will try again to make the suggested adjustments at a later date or try Chrome to see how it works.

Tried to re upgrade to 22.0, and I still get the message that Norton Vulnerability Protection is not compatible.

Update to Firefox 22, then update Norton. Regardless, you should still be running Firefox 22.

Hi marv6, here is Symantec's support article: Message: "Norton Vulnerability Protection is incompatible with Firefox 22.0" after I install the Firefox update:

You are still proactively protected from the browser-based and web-based attacks through the multi-layer protection technologies in Norton solutions including the Symantec Intrusion Prevention, Download Insight, and SONAR.

The Norton issue is still not fixed, but, that is really Norton's problem. The issue about the DPI etc. is really a Firefox problem. When I go back to 96 DPI then everything else is too small, which is why I have the windows dpi set at 120 the only other option. There is really no happy medium in that all of these fixes suggested only sort of work and before Firefox 22.0 there was no problem.

I recently found out that TV listings site is no longer supported, too bad they did not put up a note explaining that!

Had a bad malware infestation that took many weeks to clear out and re-install corrupted software etc. Sorry for the late response, but that is the reason.

I did the required Firefox changes and installed the Theme Font & Size Changer and am able to view my pages much easier now and the CTRL +/- is working well again. Thanks for posting that. This fix though is going to be very difficult for people who have their first computers or are not too computer savvy. It has done the trick for me though thank goodness.