Closed
Bug 1134785
Opened 10 years ago
Closed 7 years ago
tabs.open fails if no window is open
Categories
(Add-on SDK Graveyard :: General, defect, P2)
Add-on SDK Graveyard
General
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: jamie, Unassigned)
References
Details
Attachments
(1 file)
1.58 KB,
application/zip
|
Details |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_2) AppleWebKit/600.3.18 (KHTML, like Gecko) Version/8.0.3 Safari/600.3.18
Steps to reproduce:
As I realized while chatting in IRC #jetpack today, this probably only affects Mac because other platforms don't have a concept of keeping an app running after the last window is closed.
1Password supports opening URLs for filling from the main app and the helper app. Depending on the state of the browser (whether it has focus, whether there is a window, whether the frontmost tab has a URL) and the user's settings (open in a new tab, current tab, or new window) 1Password needs to reason about the environment and respond appropriately.
We can identify when we think a tab does not actually exist (See Bug #1134699 for why we can't be 100% certain…) and attempt to open a tab. But, tabs.open fails when there is no window.
Run the attached example add-on. The first time, let the new window stay open. The second time, close the new window as soon as it opens before the timer fires.
Actual results:
When a window is present, the tab is properly opened. When a window is not open, the tab is not opened.
Expected results:
The tab should always open when tabs.open is called.
Comment 1•7 years ago
|
||
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
Comment 2•7 years ago
|
||
You need to log in
before you can comment on or make changes to this bug.
Description
•