Closed
Bug 308029
Opened 20 years ago
Closed 20 years ago
Thunderbird ignores first line of mcd autoconfig (1.5 beta 1)
Categories
(Thunderbird :: Preferences, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: Richard.Burkert, Assigned: mscott)
References
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6
Build Identifier: Thunderbird 1.5 Beta 1 (20050908)
Thunderbird completely ignores anything on the first line of my mcd autoconfig
file. The first line doesnt appear to be parsed at all, i can fill it with
garbage even and it wont cause a syntax error. Anything 2nd line and on works.
Reproducible: Always
Steps to Reproduce:
1. create test autoconfig file in thunderbird binary directory,
displayError("line 1");
displayError("line 2");
2. configure thunderbird for autoconfig in greprefs/all.js,
pref("general.config.obscure_value", 0); // for MCD .cfg files
pref("general.config.filename", "my_test_autoconfig.cfg");
3. run thunderbird, note which error displays
4. close thunderbird, edit the test autoconfig file and insert a blank line (or
line of garbage, or whatever) at the top, and save
5. run thunderbird again, note which error displays
Actual Results:
on the first run, the "line 2" error displays. on the second run, the "line 1"
error displays (and after dismissing the error dialog, the line2 error displays).
Expected Results:
the first run should have given results like the 2nd, i.e. the line1 error on
the first line should not have been skipped.
fresh install of 1.5 beta 1 on win xp sp2
| Reporter | ||
Updated•20 years ago
|
Version: unspecified → 1.5
I can confirm this. After half an hour of debugging and googling I stumbled upon this bugreport.
Comment 2•20 years ago
|
||
this is by design. We should make sure this is documented. We can't change this since that could break everyone who knew that the first line was ignored and put garbage there.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•