Reply to thread

Message

<blockquote data-quote="i7ii" data-source="post: 1118866" data-attributes="member: 116614">Dito. And there&#039;s not even a need to use an external text editor - for editing those, not need to touch those files either (unless you use one made by another - replacing default) - you can do all that within the browser, by typing: about:config in&nbsp; address bar. They save instantly - as soon as you press enter. You can also add some missing entries (if not present there). Clicking on Show Only Modified Preferences - will show you all the changes made (from Default) - even the option to revert to Default - if a setting was changed from about:config.At times, Firefox shoots itself in the foot - by playing the same tricky game as Chrome - to get some extra points in &quot;synthetic benchmarks&quot;. Rather stupid at times, like setting: nglayout.initialpaint.delay &amp; nglayout.initialpaint.delay_in_oopif to 5 as Default setting. Which can be rather demanding for many systems or phones - using FF - thus, on heavy pages - one could notice a slight strugle to render the page at that speed. Around a decade ago - this setting was set to 250 - which shows more common sense as&nbsp; &quot;default setting (for every macine using it)&quot;. So hey, if your system - was powerfull enough - you could lower the value and notice a faster loading page. But... 5, is just to low - formany machines.&nbsp; Thus, to get the best of both worlds - setiing it to more reasonble values like 50 or even 100 - can actually be an improvment &quot;for most systems and the human eyes&quot; - since now it has enough time to render the content &quot;more smoothly&quot; - avoiding a visable imput lag (as if it&#039;s chocking - before rendering the whole page &quot;if a heavy page that is&quot; ).</blockquote>

[QUOTE="i7ii, post: 1118866, member: 116614"] Dito. And there's not even a need to use an external text editor - for editing those, not need to touch those files either (unless you use one made by another - replacing default) - you can do all that within the browser, by typing: [B]about:config [/B]in address bar. They save instantly - as soon as you press enter. You can also add some missing entries (if not present there). Clicking on [B]Show Only Modified Preferences - [/B]will show you all the changes made (from Default) - even the option to revert to Default - if a setting was changed from about:config. At times, Firefox shoots itself in the foot - by playing the same tricky game as Chrome - to get some extra points in "synthetic benchmarks". Rather stupid at times, like setting: nglayout.initialpaint.delay & nglayout.initialpaint.delay_in_oopif to 5 as Default setting. Which can be rather demanding for many systems or phones - using FF - thus, on heavy pages - one could notice a slight strugle to render the page at that speed. Around a decade ago - this setting was set to 250 - which shows more common sense as "default setting (for every macine using it)". So hey, if your system - was powerfull enough - you could lower the value and notice a faster loading page. But... 5, is just to low - formany machines. Thus, to get the best of both worlds - setiing it to more reasonble values like 50 or even 100 - can actually be an improvment "for most systems and the human eyes" - since now it has enough time to render the content "more smoothly" - avoiding a visable imput lag (as if it's chocking - before rendering the whole page "if a heavy page that is" ). [/QUOTE]

Verification