8
edits
Firefox/Feature Brainstorming:Privacy: Difference between revisions
Jump to navigation
Jump to search
Firefox/Feature Brainstorming:Privacy (view source)
Revision as of 07:03, 19 July 2009
, 19 July 2009Multiple cookie management ideas: status bar pop-up menu, modern dialogs, more graceful errors, more granular preferences, etc.
(added "option to suppress referrer information to third-party domains".) |
(Multiple cookie management ideas: status bar pop-up menu, modern dialogs, more graceful errors, more granular preferences, etc.) |
||
| Line 65: | Line 65: | ||
I don't mean the same as in ''' | I don't mean the same as in '''Persistent Cookies''' down there... | ||
| Line 126: | Line 126: | ||
<tr><td> | <tr><td> | ||
; Improved Cookie Management | ; Improved Cookie Management | ||
* Merge the "Exceptions" and "Show Cookies" dialogs under Tools:Options:Privacy into the same interface as the "History"/"Library" window (perhaps adding a new "tab" bar at the top of the "History:Show All History" window). | |||
* Similar to the pop-up blocker menu in the status bar -- and perhaps sharing code -- add a cookie management pop-up menu on the right edge of the lower status bar. Menu options might include "Block"/"Allow"/"Allow for session" for the current parent site, indicating the current setting with a checkmark; and at the top (most distant pointer travel), a list of domains within the current window or tab's parent/frames/iframes/embeds, each with sub-menus of cookie names stored or requested-but-blocked, each with a sub-sub-menu to "Block", "Allow", "Allow for session", "View/Edit" or "Delete" by individual cookie name.<br> <br>This might allow the pesky ancient "Confirm setting cookie" modal dialog to be terminated with extreme prejudice (which sometimes shows up empty, or with inoperable buttons if a window's title bar is being dragged to reposition it at the time the "Confirm setting cookie" dialog is spawned, or repeatedly for the same domain in succession if the site attempts to set multiple cookies before the first dialog receives a response from the user). | |||
* Offer separate global preference default settings for cookies from secure vs. unsecured URLs (e.g., "Allow" for secure URLs such as banks/shopping cart checkouts vs. "Allow for Session" for unsecured URLs). | |||
* For cookie status "Exceptions" that Firefox has been adding automatically, only store "Exceptions" that vary from the current global default setting of "Allow"/"Allow for Session"/"Block". (But if the global default setting is later changed, preserve/retain all prior values ''including'' those matching the new global setting.) This would shorten "Exceptions" lists dramatically, and make them a far less horrific affront to privacy concerns. | |||
* On the [http://drupal.org/files/issues/redirect_error.jpg "Redirect Loop" error page], add radio buttons to set the site's cookie status to "Allow" or "Allow for Session" when the "Try Again" button is clicked, with the "Allow for Session" radio button marked by default (since presumably the user would prefer "Block" when possible). | |||
* Devise a meta tag standard that allows sites to identify their "cookies required" error pages as such, enabling any browser to gracefully prompt a user whether they'd like to accept cookies, instead of forcing the user to follow all those convoluted browser-specific instructions for editing preference settings. | |||
* In the cookies management box (accessible by clicking "Show Cookies... in Privacy Options), there are two different buttons a user can click ("Remove Cookie" and "Remove All Cookies"). There should be a third button: "Block Cookie" (or just "Block"), which removes the cookie and blocks it. This would save time, as a user wouldn't need to delete the cookie and then manually block it. | * In the cookies management box (accessible by clicking "Show Cookies... in Privacy Options), there are two different buttons a user can click ("Remove Cookie" and "Remove All Cookies"). There should be a third button: "Block Cookie" (or just "Block"), which removes the cookie and blocks it. This would save time, as a user wouldn't need to delete the cookie and then manually block it. | ||
*Clicking "Remove All Cookies" should display an "Are you sure?" dialog box to prevent accidental cookie clearing when trying to delete a specific cookie. There should be the option of turning this off in About:Config or by some other means. | *Clicking "Remove All Cookies" should display an "Are you sure?" dialog box to prevent accidental cookie clearing when trying to delete a specific cookie. There should be the option of turning this off in About:Config or by some other means. | ||
*A user should be able to select multiple cookies with the Ctrl and Shift buttons (or their Mac equivalents). | *A user should be able to select multiple cookies with the Ctrl and Shift buttons (or their Mac equivalents). | ||
</td><td> | </td><td> | ||