Closed
Bug 1152039
Opened 9 years ago
Closed 9 years ago
The alarm api still firing at the wrong time
Categories
(Firefox OS Graveyard :: Gaia::Clock, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: Jamie_, Unassigned)
Details
with more than one alarm set some will go off at improper times
Flame
appid {3c2e2abc-06d4-11e1-ac3b-374f68613e61}
apptype b2g
vendor Mozilla
name B2G
version 3.0.0.0-prerelease
appbuildid 20150407010204
platformbuildid 20150407010204
platformversion 40.0a1
geckobuildid 20150407010204
geckoversion 40.0a1
changeset ab0490972e1e
locale en-US
os B2G
hardware qcom
processor arm
compiler eabi
Steps to reproduce
1.) open clock application
2.) set separate alarms for different times
3.) wait for the first alarm to trigger
4.) wait for second alarm to trigger
what happens:
I had several alarms set, one for 800 the other for 1200 one for 1800 and one for 2200, the first two went off the 1200 went off then the one set for 2200 went off at 1539.
what should have happened:
The alarms should have gone off at the assigned times
I am referencing Bug 1118272 which has been fixed but this problem is still occurring.
|
Reporter | |
Comment 1•9 years ago
|
||
this is no longer occurring for me so i am marking this as works for me.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•