47253 - imageblocker.enabled removed from prefs.js after changing Preferences

Status: VERIFIED WORKSFORME

(Core :: Preferences: Backend, defect, P3)

Description

[sairuh (rarely reading bugmail)]

found this using the branch [pr2/comm] bits on linux [2000.08.01.04-m17]. pls
lemme know if this also occurs in the trunk, or on other platforms, or even in
mozilla bits. if this isn't a problem in the trunk or in mozilla, okay --tho'
sucky for commercial bits, and a new bug/regression afaik.

1. in the prefs.js for your profile add the following pref to enable the Image
Blocking Manager: user_pref("imageblocker.enabled", true);
2. start the browser, verify that Image Manager exists in the Tasks > S-P > menu
and in the Preferences.
3. in the Preferences dialog, go to Navigator and change the radiobutton under
"When Navigator starts up display:" from Home Page to Blank Page (or, vice
versa, if you had started with a blank page).
4. click OK to save/dismiss prefs.
5. quit and restart the browser.

observe: Image Manager is no longer enabled (check places in step 2), and the
pref is no longer in prefs.js.

Comment 1

[Stephen P. Morse]

I just pulled and rebuilt a fresh mozilla and commercial tree.  I tried this out 
and did not see the problem indicated.  The imageblocking pref remained in my 
prefs.js file and indeed all the image-blocking features were active on my 
return to the browser.  Sarah, can you please retest this to make sure it is 
really failing as you described.  Thanks.

Comment 2

[sairuh (rarely reading bugmail)]

i cannot repro using a new profile with today's branch bits... however, what i
was seeing is best described in bug 47628 (confusing as it is) anyhow... gonna
mark this wfm.

Comment 3

[sairuh (rarely reading bugmail)]

vrfy.

Comment 4

[Henrik Gemal]

just got this in the console with 20010514:
"imageblocker.enabled pref is missing from all.js"

it seemed to happen after I deleted all bookmarks. Will try to see if I can 
reproduce.

Comment 5

[Viswanath Ramachandran]

nav triage: this is a Future bug and not a netscape beta stopper. 

Comment 6

[Paul Chen]

nav triage team:

Please justify why this is catfood (required for general market acceptance). 
Marking nsCatFood-.

Comment 7

[Stephen P. Morse]

What gemal is describing on 5-15 is not the bug that sairuh reported when she 
originally opened this report.  So I'm going to restore the original description 
on this bug and close it out once again as works-for-me.

Furthermore, gemal never did confirm if he can reproduce it.  If you can, them 
please open a separate bug report on the new symptom (involving bookmarks).  
Don't morph this bug.

Comment 8

[sairuh (rarely reading bugmail)]

rs vrfy.

Comment 9

[Daniel Veditz [:dveditz]]

Prefs that match the default values are not stored in prefs.js, this kind of
thing is a common problem when you use the same profile in multiple Mozilla
distributions with different default values (e.g. Mozilla and Netscape 6, or
Mozilla and Beonex). The most common complaint is probably about the "JS in
Mail" value.

See bug 58326, but until something like that is implemented (which raises other
issues) put custom values for these problematic prefs into user.js instead of
prefs.js