NoSquint properly resized web pages, but the upper taskbars are still too large--for instance, I can only the beginning of the URL. How to fix?
After the latest Firefox version magnified everything, I used the NoSquint add-on (at 60%), which now makes web pages look as they did before. However, although the top two bars at the top of the screen are of normal size, the lower ones are still too large. The bar that contains the URL on the left and a Google search space on the right, for instance, can display only the first couple of letters of a URL (after the //).
How do I make these bars look the way they used to? Thanks.
must be something else that is changing my nosquint settings when I visit different web pages and when I log in again?
Hi marv6, NoSquint should store your preferred zoom level on a site-by-site basis (same as the native Firefox zoom feature) and apply that across tabs and windows wherever the site appears. There are many reasons that saved preferences might be lost between sessions (e.g., How to fix preferences that won't save), but if it's not working even within the same session of Firefox, that's odd.
I don't use NoSquint, so I don't have any first-hand experience. If you haven't built up a lot of saved preferences in NoSquint, you could switch to the combination of Default FullZoom Level (to set the default zoom level to 80% or your preference) and then use Firefox's native zooming (Ctrl+, Ctrl-) to store site-specific variations from the default.
jscher2000 thanks for all of your help, but, until FF22.0 I never had to adjust things every time I went to a different web site. This is getting to be too much work. Now I notice that even when printing I have to now adjust to get everything to print on one page. For some reasons almost every site requires some new settings. I currently have the layout setting set at 1.1 and the pages are still too big, home page, web mail, and facebook, especially, and the headers are too small. I tried your suggestions, but must not be smart enough to get them all right. Why is all of this work necessary now when we had none of these problems with ver 21.0? I know my problem is that I have my windows DPI set at 120, instead of 96 because if set it to 96 then everything else but Firefox is too small because I have a 22 inch screen. But, once again the problem is really the current version of FF as I did not have these problems with ver 21.0. I have been using FF and Netscape since the beginning and have had some problems, but, none at this level. Because I use windows DPI 96 on my laptop it appears to have none of these problems. If firefox does not fix this soon, I will have to go back to ver 21.0 and hope that my Norton 360 continues to protect me.
Hi marv6, with your device pixels setting at 1.1, the text and images on page should be 10% larger than in Firefox 21. If you are seeing a bigger difference, then it could be caused by a combination of your global zoom settings and stored site-specific zoom levels in NoSquint. I'm not familiar with how to efficiently reset those values.
For printing, did the "Shrink to Fit" box get unchecked? You can set that in Page Setup, or on the toolbar in print preview.
Hi marv6, when you say "the headers are too small" do you mean in the web pages or in the user interface?
With your device pixel ratio set to 1.1 and your Windows DPI set at 120, the user interface will be about 12% smaller than your other Windows UI settings (and 12% smaller than in Firefox 21):
Firefox UI: 96ppi x 1.1 = 105.6ppi Compared with Windows: 105.6ppi/120ppi = 0.88
It's hard to find a device pixel ratio that effectively compromises both the chrome area (menu, toolbar, tab) and the content area. For most people, it will be simpler to optimize one area and compensate the other area with an add-on as needed.
For example, if you want to eliminate scaling for the content area, set the ratio to 1.0 and use the Theme Font & Size Changer extension to increase the fonts in the UI.
I mean the user interface, all of the stuff at the top, Firefox, tabs, bookmarks, icons, etc. We did not need to do all of this adjusting with FF 21.0, so to me this is a step backwards, not forward.