Closed
Bug 1248903
Opened 8 years ago
Closed 7 years ago
High-Level APIs Windows brokens in private mode
Categories
(Add-on SDK Graveyard :: General, defect)
Add-on SDK Graveyard
General
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: zepeuj, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:44.0) Gecko/20100101 Firefox/44.0 Build ID: 20160210153822 Steps to reproduce: The problem can be reproduce with this simple code: const windows = require("sdk/windows").browserWindows; windows.on("activate", function(window) { console.log("A window was activated."); console.log("Active window title: " + windows.activeWindow.title); // => tabs length is always 0 !!!! console.log("Active window tabs length: " + windows.activeWindow.tabs.length); }); windows.on("open", function(window) { // => event not detected console.log("window open"); }); const tabs = require('sdk/tabs'); tabs.on("activate", function (tab) { console.log("A tab was activated."); try { console.log("Active window tabs length: " + tab.window.tabs.length); } catch (e) { // => exception because the window associated to the tab is null !!! console.log(e); } }); Of course the following key must be set in the package.json file of the add-on: "permissions": {"private-browsing": true} To reproduce the problem Firefox must be STARTED with a private window. Actual results: So the problems: * The private window opened is not detected by the "open" event * The active window cannot list the tabs. * The active tab cannot get the associated window. Important: this only happens if Firefox STARTS with a private window. If another private window is opened, the problem doesn't happen with this window. If Firefox is started in normal mode and a private window is opened, the problem doesn't happen with this private window. Expected results: The expected behavior is the same than with not private windows.
Comment 2•7 years ago
|
||
https://bugzilla.mozilla.org/show_bug.cgi?id=1399562
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•