279782 - Initial setting of "Image Acceptance Policy" category is broken.

Status: RESOLVED FIXED

(SeaMonkey :: General, defect)

Description

[hub-san]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b) Gecko/20050125
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b) Gecko/20050125

When I do first execution of Mozilla suite, initial setting of "Image Acceptance
Policy" on GUI is broken.  Radio button of "Accept all images" should be
selected at "Image Acceptance Policy" by default.



Reproducible: Always

Steps to Reproduce:
1. Delete or rename old profile directory.
2. Do first execution of Mozilla suite.
3. Goto Edit>Preferences...>Privacy & Security>Images 

Actual Results:  
No radio button is selected at "Image Acceptance Policy" category.


Expected Results:  
Radio button of "Accept all images" is selected at "Image Acceptance Policy"
category by default.



I confirmed this problem on 2005-01-03-06-trunk of Mozilla suite(MacOSX10.2.8).
 2005-01-25-05-trunk of Mozilla suite is still broken.  2004-12-16-06-trunk
already had this bug.  But, 2004-12-15-06-trunk didn't have this bug.  This
regression occurred between 20041215 and 20041216.  This problem is related to
bug 256172.

Comment 1

[Michiel van Leeuwen (email: mvl+moz@)]

Attachment: set all.js

oops. Forgot to set all.js to a default.

Comment 2

[Mats Palmgren (inactive)]

Maybe this fixes bug 279535 also?

Comment 3

[Darin Fisher]

Comment on attachment 172368 [details] [diff] [review]
set all.js

sr=darin

Comment 4

[Michiel van Leeuwen (email: mvl+moz@)]

patch checked in

Comment 5

[hub-san]

I confirmed the problem that "permissions.default.image" is always set to 1. 
When "Accept images that come from the originating server only" is selected, the
setting is back in "Accept all images" after restarting Mozilla. 
2005-01-29-06-trunk(MacOSX) had already this problem.  2005-01-28-05-trunk
didn't have this problem.  Should I report this problem as another bug?  Or
should I reopen this bug?

Comment 6

[Michiel van Leeuwen (email: mvl+moz@)]

that has now been reported and fixed in bug 280670