Adjust the design of site exceptions in Settings to account for persistent mode
Design estimate
- Complexity: TBD
- Uncertainty: TBD
- Total: TBD
- Actual:
Context
Currently, there are 2 possible browsing modes for users:
- Normal mode: the data is saved in the disk, which means that the browser will remember information even after it is shut down.
- Private mode: the information is saved on memory, but not in the disk, which means that the browser will remember information within a session, but not after it is shut down.
We want to offer a new mode called Persistent mode, that keeps only specific information (e.g. cookies and passwords) in the disk. These information will be available in the browser in any newer sessions after it is closed; other data, however, will be deleted.
Once shipped, Persistent mode will replace Normal mode [1].
[1] It's possible for power users to still enable Normal mode by editing configuration options directly in about:config
, but that's very difficult for regular users + won't be supported at all.
Scope
- Adjust the UI of site exceptions to account for persistent mode;
- Adjust the copy, when needed.
Out of scope
- Changes to any other part of the Settings page but the list of site exceptions;
- Any changes to the browser chrome.
References
Current component for the list of persistent mode: websites with "Allow" status are using persistent mode
Useful links
- Pad: Persistent mode sync
- Pad: Persistent mode hacking (in-person meeting)
- CSD matrix
Mockups
TBD
Acceptance criteria
TBD
Edited by Felicia