Open
Bug 1068578
Opened 10 years ago
Updated 2 years ago
mozAlarm.add fails if third optional argument is omitted
Categories
(Core :: DOM: Core & HTML, defect, P5)
Tracking
()
UNCONFIRMED
People
(Reporter: jehan+mozillabugs, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:32.0) Gecko/20100101 Firefox/32.0
Build ID: 20140830210550
Steps to reproduce:
- Install Openwapp on FxOS 2.1
- open application
- screen remains white because code is blocked here (1)
This is due to (2), which sandboxes the third argument of mozAlarm.add, which means that if no argument is there it fails. I tested modifying the call to add a third dummy argument ({}) and the app works again.
(1) http://git.ovz.ca/openwapp/openwapp/blob/master/app/scripts/models/background-service.js#L82
(2) http://mxr.mozilla.org/mozilla-central/source/dom/alarm/AlarmsManager.js#75
See openwapp discussion here: http://git.ovz.ca/openwapp/openwapp/issues/129
Actual results:
mozAlarm.add() call blocked the whole application.
Expected results:
mozAlarm.add() call should have succeeded.
Comment 1•6 years ago
|
||
https://bugzilla.mozilla.org/show_bug.cgi?id=1472046
Move all DOM bugs that haven’t been updated in more than 3 years and has no one currently assigned to P5.
If you have questions, please contact :mdaly.
Priority: -- → P5
Assignee | ||
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•