Closed
Bug 1432605
Opened 7 years ago
Closed 7 years ago
WebExt alarms do not work between files (eg background.js and popup.js)
Categories
(WebExtensions :: Untriaged, defect)
Tracking
(firefox60 verified)
VERIFIED
FIXED
mozilla60
Tracking | Status | |
---|---|---|
firefox60 | --- | verified |
People
(Reporter: fx4waldi, Assigned: kmag)
References
Details
Attachments
(3 files)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:60.0) Gecko/20100101 Firefox/60.0
Build ID: 20180123102017
Steps to reproduce:
1. Create a new alarm in the background.js file, e.g.
browser.alarms.create("background",{periodInMinutes:0.1});
2. Create a new onAlarm event in background.js file e.g.
browser.alarms.onAlarm.addListener(alarm=>{console.log(alarm);});
3. Create a browserAction button with a popup.
4. Create a new alarm in the popup.js eg.
browser.alarms.create("popup",{periodInMinutes:0.1});
5. Install the extension.
6. Open the browser console (ctrl+shift+j)
7. Everything is fine, the log is displayed every 6 seconds.
8. Open the popup.
9. Alarms stop working.
Alternative STR:
1. Install the extension from attachment.
2. Open the browser console (ctrl+shift+j)
3. Everything is fine, the log is displayed every 6 seconds.
4. Open the popup and click the "Alarm" button.
5. Alarms stop working.
If I create an alarm via browser.runtime.sendMessage, the problem doesn't occur.
(Install the extension and click the "Message" on the popup)
Component: Untriaged → WebExtensions: Untriaged
Product: Firefox → Toolkit
Comment hidden (mozreview-request) |
Comment hidden (mozreview-request) |
Comment 3•7 years ago
|
||
mozreview-review |
Comment on attachment 8944969 [details]
Bug 1432605: Fix alarms API when multiple contexts use it.
https://reviewboard.mozilla.org/r/215108/#review221004
Attachment #8944969 -
Flags: review?(aswan) → review+
Assignee | ||
Comment 4•7 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/d22cc0f160121630d4a788d7c1fd8b8e88c4fbb0
Bug 1432605: Fix alarms API when multiple contexts use it. r=aswan
Comment 5•7 years ago
|
||
bugherder |
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
status-firefox60:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla60
Comment 6•7 years ago
|
||
I was able to reproduce the issue on Windows 10 64Bit Firefox 60.0a1 (20180122220231).
Tested and verified the issue in I was able to reproduce the issue on Windows 10 64Bit Firefox 60.0a1 (20180130102929).
Comment 7•7 years ago
|
||
Tested and verified on Windows 10 64Bit and Mac OS X 10.13.2 in Firefox 60.0a1 (20180130102929).
Status: RESOLVED → VERIFIED
Updated•7 years ago
|
Product: Toolkit → WebExtensions
Updated•6 years ago
|
Assignee: nobody → kmaglione+bmo
You need to log in
before you can comment on or make changes to this bug.
Description
•