Closed Bug 876981 Opened 12 years ago Closed 7 years ago

Expose mozAlarms API to webpages on Firefox desktop

Categories

(Core :: DOM: Device Interfaces, defect)

Product:
Core
Component:
DOM: Device Interfaces
Platform:
x86_64
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INCOMPLETE

People

(Reporter: nsm, Unassigned)

References

(
URL
)

Details

In the vein of bug 857464. Do we want this? What security issues does this entail? Not a high priority unless required.
We shouldn't expose this to random wabpages until/unless we can unprefix the API.
URL: http://www.w3.org/TR/web-alarms/
Component: DOM → DOM: Apps
Yeah, definitely shouldn't expose without unprefixing.
We could consider make that happen as a Nightly/Aurora only feature if we have plans to push that to Beta/Release.
Component: DOM: Apps → DOM: Device Interfaces
Blocks: alarm-api
No longer depends on: alarm-api
What's the plan here now? Is this API superseded by Background Sync resp. can this spec replace all use cases of mozAlarms? Or is there cross-vendor spec work going on for the additional functionality provided by the mozAlarms feature?
FxOS/Gonk has been removed from the codebase. Mass-invalidating FxOS related Device Interface bugs to clean up the component. If I incorrectly invalidated something, please let me know.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
Bulk correction of resolution of B2G bugs to INCOMPLETE.
Resolution: INVALID → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.