user_pref("nglayout.initialpaint.delay", 0);
59 posts
• Page 1 of 4 • 1, 2, 3, 4
Has anyone added this to their prefs.js file? It seems to make Phoenix screamingly fast, on par with Opera 6 even. I wonder, why isn't it enabled?
What's the meaning of this pref? If there would not be any disadvantages it was enabled by default.
This is how I understand what it means: Gecko normally delays the first paint of a page for a certain time while it is still loading to bring down the number of reflows needed to correctly show the complete page. The more reflows, the higher the total page load time. The default is 1200ms. If the rendering calculations are done before this period has elapsed, it will show it anyway. If not, it's displayed in a not yet complete state and then reflowed until it can be showed correctly. 1200ms seems to be the best compromise to give the best overall performance. If you set it to 0, painting will start almost instantly, which gives a very fast appearance, but total page load time will rise in most cases because more reflows are needed until the page reaches its final rendering state.
Well put. I guess technically it takes longer to complete, but because you can read the content sooner, the trade-off might be worth it for some people. I quite like it so far!
where must I place de prefs.js file ?
yes, i read it ! but i put it in phoenix\defaults\profile but it doesn't change anything ! (for exaple, the link when I click the logo is still mozilla.org )
I'm under winXP
@laszlo:
Thanks a lot for the detailed explanation. I think it might be worthwile to experiment with this if you are not interested in benchmark alike page load numbers, but in beeing able to start reading soon. On the other hand setting this value too low, will probably lead to rearangements of partly layed out sites.
Bitteschön 
Seems to me you're somehow putting it into the wrong directory. Did you you closely follow the instructions? There's another way to find your profile dir(s). Exit Phoenix and start it with the "-ProfileManager" commandline option. There should be at least one existing profile (usually called "default"). Click "Create Profile", then "Next". You'll see a dialog asking for a path to put the new profile in. The directory shown minus the profile name itself is the directory where the "default" profile lives in. Cancel the Profile Manager. Change to this default profile directory. You should see a "cache" dir, a "chrome" dir and several files where profile information is kept in, one of which is prefs.js. Put user.js into this directory, or carefully edit prefs.js itself accordingly. Start Phoenix, load about:config. If some of the changes don't show up, don't worry, they may not be supported by Phoenix. If you chose the user.js method, exit Phoenix again and look if prefs.js has changed (the changes from user.js should be in prefs.js now, if supported).
You did not read it! Read it again.
There has to be something wrong with these two sentences, but I'm just not able to figure out what it is
I know.  I thought about it as soon as I submitted it.
Ok Ploum, maybe you read it but you didn't understand it! Now read it and understand it.
That is the compleatly WRONG place to edit in. It's well explained in the FAQ Hint/keyword -> Application Data
I want to apologize for those stupid questions !
I was looking for folders in my Apps folder, but not the Apps data folder of my windows profile ! (I thought I remove them... but it's windows !) Many thx to Lazlo for his help ! It was very helpful ! My user.js is now
And phoenix is incredibly faster than before ! It's wonderful ! Note that I put nglayout in user.js and not in prefs.js... (just because I don't understand the difference and I prefer edit only user.js ) Do you think that I must put nglayout in prefs.js ?
Thanks for the preference it really speeds up Phoenix.
59 posts
Page 1 of 4 • 1, 2, 3, 4
Who is onlineUsers browsing this forum: Exabot [Bot] and 7 guests |
|
