Closed
Bug 714359
Opened 13 years ago
Closed 12 years ago
Implement "clockchange" event for gonk
Categories
(Core :: DOM: Device Interfaces, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 714358
blocking-basecamp | - |
People
(Reporter: cjones, Unassigned)
References
Details
For gonk this is relatively simple: only gecko will change the system time, and only through the settings API, so the notification can be keyed off changes to settings.time.timezone and settings.time.msSinceEpoch (as proposed in bug 714357).
Comment 1•13 years ago
|
||
Hi Chris,
This bug looks like related to Bug 717150, can I take it ?
Regard
Vincent
Reporter | ||
Comment 2•13 years ago
|
||
Sure! Most of the work will be defining the DOM interface in bug 714358. But we can go ahead and add the hal implementation here.
We want a hal API that for listening to "clock" changes, kind of like battery-status updates. Setting the timezone and changing the system clock will trigger the notification; the notification will originate from the hal:: APIs you added in bug 717150. You should be able to follow the example of the battery-status updates for the listener notifications.
Please let me know if you have questions.
Updated•12 years ago
|
blocking-basecamp: --- → ?
Updated•12 years ago
|
blocking-basecamp: ? → -
Comment 3•12 years ago
|
||
This one seems duplicated by Bug 714358 which has already provided a time-changed observer at the hal:gonk level.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•