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.

The only major I have had with Recent SM build is the issue with spell check That was worked around with a setting in about:config from 1 to zero I had put a bug mad all the comments I going to on it. Found if you comment too much on a Bug they disregard the bug and assume you a PIA.

Of course they never have taken me serious and considered me a PIA since my first bug report Back in Communicator Mozilla Days (forerunner to SeaMonkey). Because I am a User not a Code writer I don't know about bugs.

I do know when something use to work and it doesn't and it hasn't been pulled. On this last bug come to find out the issue was happening with Thunderbird as well and on Linux/UNIX platforms as well.

--
Phillip M. Jones, C.E.T.      "If it's Fixed, Don't Break it"
http://www.phillipmjones.net    mailto:[email protected]
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey

Reply via email to