On 10/2/2013 1:10 AM, Daniel wrote:
Desiree wrote:
On 10/1/2013 5:03 AM, Daniel wrote:
Daniel wrote:
Desiree wrote:
<Snip>
How so? The DEFAULT behavior was changed so I don't follow your
reasoning. If I had a USER designated preference and I put that in a
user.js file then that wouldn't be changed with a new version of
SeaMonkey but this happened because the default behavior was changed.
Desiree, if you set a pref in a user.js file then, each time you start
SM or FF, that pref is applied *after* the prefs.js file is read, so,
unless the pref you set is totally disabled, SM/FF will start up with
the pref set to default and then be set as per your user.js file.
Or something like that!!
Thinking further, maybe, in the start-up process, the user.js settings
might be read into the prefs.js file and then SM/FF starts up.
So, if I had known that in Fx 2.21 that the default preference would
change then, before I upgraded, I could have put the default preference
from 2.20 in my user.js file and then upgraded to 2.21 and I would not
have had the problem. But how would I know ahead of the change that it
was going to cause a problem? I'm still not getting your point.
Yes, I suppose I'm not helping you ...... this time, but maybe, next time!!
But, thinking about it, this could happen every update and to every
setting in prefs.js, so I wonder why we don't copy "our" prefs.js into
user.js before every update, ... you know, just in case!!
Yeah...but if you did that then you would never know if a change would
work ok and that maybe you would like the change.
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
