Home → Questions →

Prefs.js/config file

• Edit

Wayne Sadler

04 May, 2020 09:15 AM

For as long as I've been using TFF I've always used a modified prefs.js file based on FireFox tweaks collected from around the web and it does make a significant difference to performance.
However, on the MacRumors PPC forum, a lot of users claim to be reaping benefits from a branded config file that attempts leverage of features that as far as I understand, aren't supported eg WebGL and fast layout frame rate.
Any thoughts on this? Is it just placebo or is my Powerbook missing out? I've tried said config file and it performs worse than my exisiting one.

1. Support Staff 1 Posted by Cameron Kaiser on 04 May, 2020 03:03 PM

   

   WebGL and GPU layers acceleration are blocked at the source code level because 10.4 doesn't support OpenGL 2 or NPOT textures (required for proper function). Any pref claiming to change them is, as you say, a placebo. You can prove this: look at gfxPlatform::ShouldUseLayersAcceleration() in https://github.com/classilla/tenfourfox/blob/master/gfx/thebes/gfxP... and GfxInfoBase::GetFeatureStatusImpl() in https://github.com/classilla/tenfourfox/blob/master/widget/GfxInfoB... . Note that the function unconditionally blocks, and doesn't even check any prefs. I did this on purpose so that someone couldn't get the browser into a situation they couldn't easily get it out of.

   As far as frame rate, the original setting prior to FPR14 was -1, which was paint as fast as you can and don't throttle. Anything setting a high frame rate is essentially doing the same thing. This might help some pages but will harm others, and 30fps has been the default since FPR14. See http://tenfourfox.blogspot.com/2019/03/tenfourfox-fpr14b1-available... for more explanation.

   • Edit

2. 2 Posted by Wayne Sadler on 04 May, 2020 03:13 PM

   

   Thanks for confirming on that - I think it must be a case of people seeing what they want to see.

   • Edit

3. Support Staff 3 Posted by Cameron Kaiser on 04 May, 2020 03:22 PM

   

   Part of the issue could be them restarting the browser to check changes. That will always seem to make things faster because garbage and cycle collection time becomes negligible, even if you don't actually toggle any prefs. The acceleration prefs do no harm but they don't do anything anymore, and I should probably just remove them if people are abusing them like that to make the point clear.

   • Edit

4. 4 Posted by Wayne Sadler on 04 May, 2020 03:55 PM

   

   Well no harm done I guess, people can be left to it...even if it is somewhat delusional.
   Having access under the hood is invaluable though - the site specific user agent feature you implemented a while back is a great addition to the browsing experience.

   • Edit