Closed
Bug 370119
Opened 17 years ago
Closed 1 month ago
UE parity between popup/flashblock and cookie exception lists
Categories
(Camino Graveyard :: Preferences, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: stuart.morgan+bugzilla, Unassigned)
References
Details
The popup exception list and cookie exception list serve the same purposes, but the UE is not the same. The biggest thing missing is sorting in popups, but they should also both support filtering and adding elements. Probably we should re-thing the add UI (maybe a + button and inline host editing). As a note to myself, it's would most likely be worth making an nsIPermissionManager/nsIPermission wrapper so there doesn't need to be so much code duplication for editing, sorting, etc.
Reporter | ||
Comment 1•17 years ago
|
||
Reverse domain sorting of popup blocker exceptions goes on the list now too.
Reporter | ||
Updated•16 years ago
|
Assignee: stuart.morgan → nobody
The "Remove" button seems to be active no matter what (even if nothing) is in the WebFeatures lists. The UI for that in Privacy seems so much cleaner.
Comment 4•16 years ago
|
||
I hope I'm adding this to the right bug. It'd be really nice to be able to sort the exceptions lists for cookies, popups, flashblock (if and when), etc., by "most recently added to list". Rationale: occasionally with cookies, in particular, i click quickly and then realize that i probably didn't want to allow a given cookie. If i remember the site name, i can go into the exceptions list and find it, but i don't always remember. Just "added during this session" would be good enough. I can imagine that being easier to implement, since you wouldn't have to add the modification date to the data store.
Reporter | ||
Comment 5•16 years ago
|
||
That would be a new enhancement request. This bug is only about getting the existing functionality consistent between panes.
Summary: UE parity between popup and cookie exception lists → UE parity between popup/flashblock and cookie exception lists
You need to log in
before you can comment on or make changes to this bug.
Description
•