Privacy/Features/Virtualized permissions manager
From MozillaWiki
Please use "Edit with form" above to edit this page.
Status
enable memory-only permissions manager and site-specific prefs | |
Stage | Draft |
Status | ` |
Release target | ` |
Health | OK |
Status note | ` |
Team
Product manager | Sid Stamm |
Directly Responsible Individual | ` |
Lead engineer | ` |
Security lead | ` |
Privacy lead | ` |
Localization lead | ` |
Accessibility lead | ` |
QA lead | ` |
UX lead | ` |
Product marketing lead | ` |
Operations lead | ` |
Additional members | ` |
Open issues/risks
`
Stage 1: Definition
1. Feature overview
The permission manager should have the same functionality that the Strict Transport Security service has: when private browsing mode is enabled, changes to permissions should be kept only in memory. This way, when private mode is exited, any changes in site permissions can be rolled back.
2. Users & use cases
`
3. Dependencies
`
4. Requirements
This should be disabled by default to keep the existing Firefox behavior, but there should be a pref to turn it on for add-ons that want it. Eventually, we may toggle the pref on by default, but we need some significant testing first.
Non-goals
`
Stage 2: Design
5. Functional specification
`
6. User experience design
`
Stage 3: Planning
7. Implementation plan
`
8. Reviews
Security review
`
Privacy review
`
Localization review
`
Accessibility
`
Quality Assurance review
`
Operations review
`
Stage 4: Development
9. Implementation
`
Stage 5: Release
10. Landing criteria
`
Feature details
Priority | P3 |
Rank | 999 |
Theme / Goal | Advancing Anonymity |
Roadmap | Privacy |
Secondary roadmap | ` |
Feature list | Platform |
Project | ` |
Engineering team | ` |
Team status notes
status | notes | |
Products | ` | ` |
Engineering | ` | ` |
Security | ` | ` |
Privacy | ` | ` |
Localization | ` | ` |
Accessibility | ` | ` |
Quality assurance | ` | ` |
User experience | ` | ` |
Product marketing | ` | ` |
Operations | ` | ` |