Open Bug 1215632 Opened 9 years ago Updated 2 years ago

Unit test to assert that a browser action opens the popup in the parents mode (private vs not-private)

Categories

(WebExtensions :: Frontend, defect, P5)

Product:
WebExtensions
Component:
Frontend
Type:
defect

Tracking

(Not tracked)

People

(Reporter: evilpie, Unassigned)

Details

(Whiteboard: [browserAction]triaged) 

When the browser in private browsing mode then the browserAction popup should also probably be loaded as such. In chrome there seems to be incognito_behavior to control this behavior. See bug 1208563.
The popup should inherit the private browsing state of its parent. Do you have a reason to think it doesn't?
I tested this by adding some links to the html page in browser popup. When opening the browser popup in normal mode, the links were marked as visited, as expected. When opening the browser popup they were not marked as visited. Maybe a naive test, but let's be believe that this is working correctly.

Kris mentioned that there might not be any unit tests for this, it would be good to add those, so keeping it open for that.
Priority: -- → P4
Summary: Load the browserAction popup in private browsing mode (incognito_behavior?) → Unit test to assert that a browser action opens the popup in the parents mode (private vs not-private)
Whiteboard: [browserAction]triaged
Component: WebExtensions: Untriaged → WebExtensions: Frontend
Priority: P4 → P5
Product: Toolkit → WebExtensions
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.