Closed
Bug 109832
Opened 24 years ago
Closed 24 years ago
user.js not being read
Categories
(Core :: Preferences: Backend, defect)
Tracking
()
VERIFIED
WORKSFORME
People
(Reporter: akkzilla, Assigned: bnesse)
Details
Recent regression: Build 2001111109: user.js is no longer being read.
- Edit prefs.js and make sure you have no "font.minimum-size.x-western" pref set.
- Edit user.js and add this line:
user_pref("font.minimum-size.x-western", 17);
- Run mozilla, browse to any page. Notice fonts are the same size they were before.
| Assignee | ||
Comment 1•24 years ago
|
||
I currently have a couple of prefs ("dom.disable_open_during_load" and
"javascript.options.strict") set via user.js. This WFM with the 2001110908 Mac
OSX build. I am pulling the tree now and will test against it as soon as I have
a build.
| Assignee | ||
Comment 2•24 years ago
|
||
I just created a user.js file and added 4 user prefs to it. 1 that was already
in my prefs.js file and 3 that were not. Using a build pulled this morning, I
launched and exited Mozilla. All 4 preferences were contained in my prefs.js
file, indicating that user.js is indeed being read.
Please verify that you aren't just having a problem that is specific to the font
preference you noted.
| Reporter | ||
Comment 3•24 years ago
|
||
Sorry for the delay -- I was having startup crashes and profile-stomping
problems with yesterday's build. It's working fine now -- I think I had a
problem specific to the line I was changing. Sorry for the false alarm, thanks
for checking.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
Comment 4•24 years ago
|
||
mass verification of WorksForMe bugs: to find all bugspam pertaining to this,
set your search string to "IfItWorksForSlappyTheSquirrelThenItWFM".
if you think this particular bug is *still* an open issue, please make sure of
the following before reopening:
a. that it's still a problem with ***recent trunk builds*** on the all
appropriate platform[s]
b. provide clear steps to reproduce (unless a good test case is already in the
bug report), making sure it pertains to the original problem (avoid morphing as
much as possible :)
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•