Confirmed users
512
edits
Per-window Private Browsing: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
|||
| Line 1: | Line 1: | ||
{{FeatureStatus | |||
|Feature name=Per-window Private Browsing | |||
|Feature stage=Feature Inbox | |||
|Feature status=In progress | |||
|Feature health=OK | |||
|Feature status note=This project is currently being developed by a university student in his free time. | |||
}} | |||
{{FeatureTeam | |||
|Feature feature manager=Josh Matthews | |||
|Feature lead engineer=Josh Matthews | |||
}} | |||
{{FeaturePageBody | |||
|Feature open issues and risks=The proposed design will break every addon that uses the existing privite browsing implementation in any way (even just attempting to play nicely with entering/existing). | |||
|Feature overview=We want to move away from a global flag model of PB being enabled to a per-window model more in line with other browsers. The implementation should support per-tab private browsing as an implementation detail, but that functionality will not be exposed by default. | |||
|Feature users and use cases=Users should be able to open up a new private browsing window without interacting with their existing browsing session in any way (especially through leakage of data from one context to the other). | |||
|Feature non-goals=We do not want to expose per-tab UI for enabling/disabling private browsing. | |||
|Feature implementation plan=https://wiki.mozilla.org/Per-window_Private_Browsing has a discussion of various consumers of the existing service and the ways they will be modified. | |||
}} | |||
{{FeatureInfo | |||
|Feature priority=Unprioritized | |||
}} | |||
{{FeatureTeamStatus}} | |||
== Rationale == | == Rationale == | ||