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?
by darinwf
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 :-/