Closed
Bug 633763
Opened 13 years ago
Closed 10 years ago
Cookie confirmation dialogs should be tab-modal
Categories
(Firefox :: General, enhancement)
Firefox
General
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: gtdev, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: polish)
Attachments
(1 file)
423.77 KB,
image/png
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101203 Firefox/3.6.13 (.NET CLR 3.5.30729) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101203 Firefox/3.6.13 (.NET CLR 3.5.30729) Accepting cookies is a content-specific action that does not require an application-modal dialog. With the recent implementation of tab-modal dialogs, cookie confirmation should be done with one of those. Bug 515521 should be fixed along with this. Reproducible: Always
Updated•13 years ago
|
Severity: normal → enhancement
Yes, this would be great polish and user experience enhancement for FF 5.
Reporter | ||
Comment 2•13 years ago
|
||
This is what happens when trying to open the NatGeo website with cookie confirmation. The front page initially opened 35 cookie dialogues. While quick-clicking through all the "NO!" buttons, new ones popped up and got lost somewhere under the stack. The screenshot was made after trying to find the current topmost dialogue, and before SIGTERMing the whole mess. If it wasn't for bookmarks management, I'd have ditched this whole damn regressionfest mess in favour of Chrome or Opera a long time ago. Stop cramming in ever more useless bling and fix the basic usability issues.
A better way to handle the cookie questions would be to pop up a single window, with a list of cookies and 3 rows of checkboxes (block, accept for session and accept) with the appropriate select all buttons etc.
Comment 4•12 years ago
|
||
If you read the related bugs (below), it should be abundantly clear that fixing this will give the user an alternative to killing firefox. Technically "polish" is not wrong, but this "enhancement" will turn major bugs into normal ones. Comment #3 would likely resolve most of these. see: bug 427184 replace pop-up cookie prompt dialog with use of information bar bug 434971 Multiple cookie "confirmations" requested for same site with "ask me every time" bug 515521 – All pending cookie popups for a given domain should be handled when one of them is in the cookie confirmation dialog bug 616843 A number of modal prompts should be made tab-modal See links for bugs in comment #10: bug 426114 comment #2 – Multiple accept popups for the same cookie. 50+! bug 420155 Large number of cookies come in and the active dialog does not always have the focus bug 420512 The Cookie LEARN option cannot be stopped at once and begs many times until website stops setting cookies bug 430006 – Infinite dialog loop for cookie permission ( bug 633763 Cookie confirmation dialogs should be tab-modal ) this bug
Updated•10 years ago
|
Blocks: fxdesktopbacklog
Whiteboard: p=0
Updated•10 years ago
|
No longer blocks: fxdesktopbacklog
Flags: firefox-backlog+
Comment 5•10 years ago
|
||
We don't have cookie confirmation dialogs anymore.
Status: NEW → RESOLVED
Closed: 10 years ago
Flags: firefox-backlog+
Resolution: --- → WONTFIX
Updated•10 years ago
|
Whiteboard: p=0
Comment 6•10 years ago
|
||
(In reply to :Gavin Sharp (email gavin@gavinsharp.com) from comment #5) > We don't have cookie confirmation dialogs anymore. Not per default but we still have them if you have custom cookie settings in the Privacy tab. Some people still use those as bug 440973 suggests. I'd say we either we rip them out or make them tab-modal.
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
Comment 7•10 years ago
|
||
We should definitely rip them out, AFAIK they have all sorts of issues.
Status: REOPENED → RESOLVED
Closed: 10 years ago → 10 years ago
Resolution: --- → WONTFIX
Comment 8•10 years ago
|
||
(In reply to :Gavin Sharp (email gavin@gavinsharp.com) from comment #7) > We should definitely rip them out, AFAIK they have all sorts of issues. I found out that there already is bug 546746 for that.
Blocks: 546746
You need to log in
before you can comment on or make changes to this bug.
Description
•