Disable incognito in single process mode
Bug #1326115 reported by
Chris Coulson
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Oxide |
Fix Released
|
Medium
|
Chris Coulson |
Bug Description
Incognito mode relies on having a separate BrowserContext under the hood, but there is only one in-process RenderProcessHost in single process mode (and a RenderProcessHost can only be associated with one BrowserContext). This means that it is not possible to mix incognito and non-incognito in the same application, so we should just disable this functionality
Changed in oxide: | |
importance: | Undecided → Medium |
status: | New → Triaged |
Changed in oxide: | |
milestone: | none → branch-1.3 |
Changed in oxide: | |
milestone: | branch-1.3 → branch-1.4 |
Changed in oxide: | |
status: | Triaged → Fix Released |
assignee: | nobody → Chris Coulson (chrisccoulson) |
To post a comment you must log in.
Le 03/06/2014 21:39, Chris Coulson a écrit :
> Public bug reported:
>
> Incognito mode relies on having a separate BrowserContext under the
> hood, but there is only one in-process RenderProcessHost in single
> process mode (and a RenderProcessHost can only be associated with one
> BrowserContext). This means that it is not possible to mix incognito and
> non-incognito in the same application, so we should just disable this
> functionality
Or make that a boot parameter for the clients (browser/webapp)?