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.
--
Daniel
User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:21.0) Gecko/20100101
Firefox/21.0 SeaMonkey/2.18 Build identifier: 20130418192405
or
User agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101
Firefox/24.0 SeaMonkey/2.21 Build identifier: 20130827183508
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
