Closed
Bug 1405265
Opened 7 years ago
Closed 6 years ago
Allow window.close after chrome.tabs.create() for extension-local pages
Categories
(WebExtensions :: Frontend, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1409375
People
(Reporter: extensions, Unassigned)
References
Details
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36 Steps to reproduce: chrome.tabs.create({ url: 'pages/index.html' }) Actual results: calling window.close in index.html logs an error on the console: Scripts may not close windows that were not opened by script Expected results: window.close should be allowed in this scenario, effectively closing the tab. fwiw, google chrome handles it that way.
tracking-firefox57:
--- → ?
Updated•7 years ago
|
Component: Untriaged → WebExtensions: Frontend
Product: Firefox → Toolkit
Updated•7 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
Updated•7 years ago
|
tracking-firefox57:
? → ---
Comment 2•6 years ago
|
||
I am reopening because bug 1301227 isn't quite the same thing. There is a flag allowScriptsToClose in the windows.create() call but there is no such thing in tabs.create().
Comment 3•6 years ago
|
||
Never mind, this is a duplicate of bug 1409375. I thought that I've seen this already but couldn't find it.
Status: REOPENED → RESOLVED
Closed: 7 years ago → 6 years ago
Resolution: --- → DUPLICATE
Updated•6 years ago
|
Product: Toolkit → WebExtensions
You need to log in
before you can comment on or make changes to this bug.
Description
•