nglayout.initialpaint.delay

Hello..
Ive read some tweaks about firefox that suggest altering the above value
may improve rendering speed.Firstly what is the views here of that tweak?
and secondly the value that mines set at is 600 and no matter what i do i
cant change that.Ive altered it in about:config and altered the pref.js
file with notepad but upon restarting firefox the 600 value is there
again.Any ideas what may be causing this?Im using latest official version
(not beta2)
me

bassbag

bassbag wrote:
> Hello..
> Ive read some tweaks about firefox that suggest altering the above value
> may improve rendering speed.Firstly what is the views here of that tweak?
> and secondly the value that mines set at is 600 and no matter what i do i
> cant change that.Ive altered it in about:config and altered the pref.js
> file with notepad but upon restarting firefox the 600 value is there
> again.Any ideas what may be causing this?Im using latest official version
> (not beta2)
> me
about:config IS the prefs.js file. Change it either in about:config
or in prefs.js, but not both. Also, if you have a user.js file, check
to make sure the entry isn't in that. Whatever entry is in that file,
over writes the prefs.js file.

As for the initialpaint -- I think its better for those on dialup than
it is for those on dsl for something fast. The default is 250
milliseconds. So, a value of 600 is far too high, thats 600
milliseconds. Also, if you change that entry, then you also have to
change another one: content.notify.interval

See: http://kb.mozillazine.org/Nglayout.initialpaint.delay for more info

--
It comes to the end of Bill Gates long, successful life, he finds
himself in the Purgatory waiting room, when God enters . . . "Well,
Bill," says God, "I'm confused. I'm not sure whether to send you to
Heaven or Hell: you helped society enormously by putting a computer in
almost every home in the world, and yet you've also created some of
the most unearthly frustrations known to mankind. I'm going to do
something I've never done before: I'm going to let you choose where
you want to go." Bill replies, "Well, thanks, God. What's the
difference between the two?" God says, "I'm willing to let you visit
both places briefly to help you make your decision." "Okay, where
should I go first?" asks Bill. God says, "That's up to you." Bill
says, "OK, let's try Hell first." So Bill goes to Hell. It's a
beautiful, clean, sandy beach with clear waters. There are thousands
of beautiful women running around, playing in the water, laughing and
frolicking about. The sun is shining, the temperature is just right.
The whole thing looks perfect, and Bill is very pleased. "This is
great!" he tells God, "If this is Hell, I REALLY want to see Heaven!"
"Fine," says God, and off they go . . . to be continued!

In article <eehpb0$257a$>, TheNewGWTC@
4iVWMRLYahp.U7yjsIFfetn says...
> bassbag wrote:
> > Hello..
> > Ive read some tweaks about firefox that suggest altering the above value
> > may improve rendering speed.Firstly what is the views here of that tweak?
> > and secondly the value that mines set at is 600 and no matter what i do i
> > cant change that.Ive altered it in about:config and altered the pref.js
> > file with notepad but upon restarting firefox the 600 value is there
> > again.Any ideas what may be causing this?Im using latest official version
> > (not beta2)
> > me
> about:config IS the prefs.js file. Change it either in about:config
> or in prefs.js, but not both. Also, if you have a user.js file, check
> to make sure the entry isn't in that. Whatever entry is in that file,
> over writes the prefs.js file.
>
> As for the initialpaint -- I think its better for those on dialup than
> it is for those on dsl for something fast. The default is 250
> milliseconds. So, a value of 600 is far too high, thats 600
> milliseconds. Also, if you change that entry, then you also have to
> change another one: content.notify.interval
>
> See: http://kb.mozillazine.org/Nglayout.initialpaint.delay for more info
>
>

Thank you for your very knoweldgable help.I know that the about:config is
the prefs.js file and did not alter them both togeteher.I just tried both
at different times because altering either had no effect on changing the
600.It is as you rightly said though ,because i have a user.js with the
600 value in to.I can now experiment with it.Thank you too for the
mozillazine link.You have been most helpful.
Regards
me