Cookies:prompting ui: Difference between revisions

Jump to navigation Jump to search
Let's keep the language here neutral.
(Let's keep the language here neutral.)
Line 15: Line 15:
== What's the use case for this feature? ==
== 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 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.)


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.)
5

edits

Navigation menu