Closed
Bug 837777
Opened 11 years ago
Closed 11 years ago
task failure: open a 'private window and activate it' is really challenging
Categories
(Add-on SDK Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 822863
People
(Reporter: glind, Unassigned)
Details
1. new style `require("window/utils").open` goes via `WindowWatcher.openWindow`. 2. no obvious code to 'activate' a window. Yes, this has been abused in the past. The doesn't mean it shouldn't be possible. 3. `WindowWatcher` supports "getWindowByName". This would be helpful as well.
Gregg, can you elaborate a bit more on what you're needing?
Flags: needinfo?(glind)
Comment 2•11 years ago
|
||
When using `require("window/utils").open` use a `private` flag (example 1) to open a private window, also bug 822863 allows you to open a private window with the top level module (ex 2). To activate a window just call window.focus() in the former example, and use window.activate() in the latter top level example. > 3. `WindowWatcher` supports "getWindowByName". This would be helpful as well. can you make this a separate issue please?
Status: NEW → RESOLVED
Closed: 11 years ago
Flags: needinfo?(glind)
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•