148
edits
Cookies:prompting ui: Difference between revisions
Jump to navigation
Jump to search
→What to do about it?
| Line 10: | Line 10: | ||
https://bugzilla.mozilla.org/show_bug.cgi?id=448438 | https://bugzilla.mozilla.org/show_bug.cgi?id=448438 | ||
== What | == What's the use case for this feature? == | ||
1) The user is obsessed with privacy and wants to see each and every cookie going through the browser, accepting and rejecting them by hand. (For instance, they might reject all cookies from a site they're casually browsing to once; but accept a login cookie, and whitelist it, for a site they frequent and manually reject third party advertising cookies from the same pageload.) | 1) The user is obsessed with privacy and wants to see each and every cookie going through the browser, accepting and rejecting them by hand. (For instance, they might reject all cookies from a site they're casually browsing to once; but accept a login cookie, and whitelist it, for a site they frequent and manually reject third party advertising cookies from the same pageload.) | ||
| Line 18: | Line 16: | ||
2) The user is curious and wants to see what's happening, and later turns prompting off. (Perhaps a webdeveloper wants to see, or debug, cookies associated with their page.) | 2) The user is curious and wants to see what's happening, and later turns prompting off. (Perhaps a webdeveloper wants to see, or debug, cookies associated with their page.) | ||
3) | 3) Other ideas? | ||
== How do we make it more better? == | |||
Two basic choices: improve the modal blocking dialog to make it less annoying, or switch to something not involving blocking dialogs (an async approach). | |||