Netscape DevEdge Update
Tuesday November 12th, 2002
#1 Why user prefs.js and not user.js?
Tuesday November 12th, 2002 5:05 PM
I am always amazed that even "official" documents like the one about bypassing the security restrictions for java recommend to edit prefs.js instead adding the preference in the user.js file. Is there a reason for this?
#3 Why user user.js and not prefs.js?
Tuesday November 12th, 2002 11:14 PM
My question might sound dumb to you, but what's the exact reason? If Mozilla is closed and I know what I do, is the problem while editing prefs.js directly? And if Mozilla is not closed, there's no danger either, since it just overwrites my changes.
Ok, don't edit prefs.js directly but edit user.js. I got the message. But in order to remember that, I must know a good reason for that. And just poking around NOT to do that without giving a reason misses the point. No offense, Johann, but if you want people to stop doing that, they need a compelling reason.
#4 Re: Why user user.js and not prefs.js?
Wednesday November 13th, 2002 12:23 AM
because prefs.js is a generated file as the comments at the top of the file state. any changes you make to prefs.js may get overwritten, deleted, or otherwise trashed. of course, in practice it almost always is just as good as editing user.js :-/
#5 Re: Why user user.js and not prefs.js?
Wednesday November 13th, 2002 5:31 AM
See bug 142590: http://bugzilla.mozilla.org/show_bug.cgi?id=142590
#9 No offensem eiseli
Wednesday November 13th, 2002 8:37 AM
but you are completely missing my point: what I am wondering about is that those people who should know best are recommending to edit the wrong file.
#11 re:No offense eiseli
Wednesday November 13th, 2002 12:08 PM
Because you can edit any of the 2. However, prefs.js has a lot of default settings, so its easier to find a pref you want to change.
#6 Re: Why user user.js and not prefs.js?
Wednesday November 13th, 2002 7:00 AM
> ...security restrictions for java...
#8 my mistake
Wednesday November 13th, 2002 8:34 AM
#2 toolbars don't work in Phx? Didn't install. n/t
Tuesday November 12th, 2002 10:23 PM
#10 Re: toolbars don't work in Phx? Didn't install. n/
Wednesday November 13th, 2002 10:26 AM
Phoenix decided to break compatability with Mozilla. Its only intended to work in Netscape 7/Mozilla 1.0 and higher.
#7 Default page when requested URL won't load
Wednesday November 13th, 2002 8:19 AM
as Mozilla would loose the original URL of a "open in new tab" page, wouldn't be great to have a default "Press Refresh to try to reload URL xxx" like in explorer? Is this allready reported/asked?