InformAction Forums

Hi Giorgio

Thanks for the smart protection tool that NoScript is, I've been using it for sometime now and have never had any major problems with it. I'm still using Firefox 3.0.19 as I noticed 3.5x upwards used a lot more memory and became sluggish with the larger memory size whereas 3.0.19 works really well and still stays more responsive when memory use increases, so I've stayed with that version of Firefox as I find it much more robust and efficient in the way I use it.

I upgraded NoScript recently and then noticed my basic browser fonts became larger on certain websites or on certain areas of a website, basically anywhere the browser font is used, my font setting is Arial 16. I thought it was an issue with something else until I disabled NoScript in the Firefox Add-ons. I then upgraded to the very latest 1.10 version and it was still the same. so I went back through each version via the archives on the download links and found that 1.9.9.97 was ok, so something you have changed in 1.9.9.98 is causing the basic browser font to show larger than it should be, my size is 16pt and with the problem I would say that it showed at about the size of 20pt.

At first I realised I could reduce the browser font size as a work-around, but then form entry boxes would become too small and so would other proportional fonts, so I've now had to go back to NoScript version 1.9.9.97 until the issue is resolved and I did find it strange that NoScript would interfere with the browsers font sizes as it shouldn't need to be associated with them, but I have proved without a doubt that versions 1.9.9.98 onwards do cause Firefox 3.x to display it's font slightly larger on the pages that display it.

I'm also surprised that it hasn't been reported here yet, but then it's only on certain webpages that it will be noticed, the first place I noticed it was on my SpamAssassin Configuration page via cPanel, where certain fonts on blacklist entries became much larger, then I noticed in on another site where the fonts in trading records became larger and pushed the whole page out of it's borders.

I hope you are able to find it and fix it.

Thanks ...John

Where, how do you get to "SpamAssassin Configuration page via cPanel"?

Other URLs where this happens?

Care to post some before/after pics?

Hm… maybe some Firefox-3.0-related issue?
Please check if the bug still persists with Firefox 3.6.6, version 3.0 is not supported anymore so you should just upgrade ASAP anyway.

therube wrote:Where, how do you get to "SpamAssassin Configuration page via cPanel"?

Other URLs where this happens?

Care to post some before/after pics?

Hi

If you used web hosting via cPanel and had SpamAssassin then you'd know where I meant, this was just one of the places I first noticed it. Most of the places I've noticed it so far are via secure access so I can't share those URLs and have just made some screen-shots as follows:





Notice how much larger the browser text gets, which affects other pages I use and why is NoScript interfering with it when it is a script protection tool and shouldn't interfere with the browsers font size, it never has until version 1.9.9.98, perhaps it's ok with Firefox 3.5+ but many like myself went back to 3.0.1x as it has less memory leakage and seems better overall if you use it for loading large records i.e. server statistics, I just find it more robust and more responsive than 3.5+, 3.6+ but haven't tested the very latest, but am really ok with my current Firefox and it also still gets security updates, so it is current. I'll just stay with NoScript 1.9.9.97 for a while if it can't be fixed.

Regards ...John

Does the problem go away if you set the noscript.surrogate.enabled about:config preference to false?

JohnDN wrote:but am really ok with my current Firefox and it also still gets security updates, so it is current.

That's not correct. The Firefox 3.0.x line received its final update to 3.0.19 on March 30. It is end-of-life and no longer secure. There have been and will be no more security updates for it. Since the release of Fx 3.0.19, Fx 3.5.x has received nine vulnerability patches that were not rolled into a Fx 3.0.x update.

https://wiki.mozilla.org/Releases/Firefox_3.0.19
http://www.mozilla.org/security/known-v ... fox35.html

JohnDN wrote:but am really ok with my current Firefox and it also still gets security updates, so it is current.

According to the plan, 3.0.19 is the last update and there will be no more official updates by Mozilla.

/edit:

Giorgio Maone wrote:Does the problem go away if you set the noscript.surrogate.enabled about:config preference to false?

Hi Giorgio

Thanks for the response, I couldn't check straight away but have just installed NS 2.0 to try your suggestion and it isn't doing it now, so perhaps you've corrected it in version 2.0.

As for the other feedback posts then I still prefer this earlier version of Firefox (3.0.19) as the memory it uses in Windows XP doesn't seem to grow as fast and so it is more responsive when many demanding windows are in use, but I'll soon check the latest Firefox version to see if the memory handling has improved.

Thanks, regards ...John

PS. I corrected the term 'surrogates' to 'surrogate' (no 's') in the quoted section above for the config option and will try that if the problem returns.

Indeed it affected Firefox 3.0.x only and it's fixed in NoScript 2.0.