Closed Bug 578467 Opened 15 years ago Closed 15 years ago

xpinstall.whitelist.add prefs are not emptied when converted into permissions on startup with new profile

Categories

(Toolkit :: Add-ons Manager, defect)

defect
Not set
normal

Tracking

()

VERIFIED FIXED
mozilla2.0b3
Tracking Status
blocking2.0 --- final+

People

(Reporter: iannbugzilla, Assigned: bparr)

Details

Attachments

(1 file)

Steps to reproduce 1/ Move .mozilla/firefox profile out of the way 2/ Start trunk build of firefox 3/ Look at about:config Expected Result 1/ Entries for xpinstall.whitelist.add should be user set with empty strings. Actual Result 1/ Entries for xpinstall.whitelist.add show default with their default values.
Do we have documentation how this feature has to work in detail? I haven't used that preference so far. As what I can see we never obey those values. Even adding another value later doesn't add the domain to the whitelist.
blocking2.0: --- → ?
This is a blocker as it means we will re-import permissions that users have removed. One line patch, should be simple if someone wants to take it.
blocking2.0: ? → final+
Assignee: nobody → bparr
Attached patch Patch and TestSplinter Review
Attachment #458929 - Flags: review?(dtownsend)
Comment on attachment 458929 [details] [diff] [review] Patch and Test Nice work.
Attachment #458929 - Flags: review?(dtownsend) → review+
Status: NEW → RESOLVED
Closed: 15 years ago
Flags: in-testsuite+
Flags: in-litmus-
Resolution: --- → FIXED
Target Milestone: --- → mozilla2.0b3
Verified fixed with Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0b5pre) Gecko/20100826 Minefield/4.0b5pre
Status: RESOLVED → VERIFIED
OS: Linux → All
Hardware: x86 → All
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: