[meta] Service Worker spec compatibility issues
Categories
(Core :: DOM: Service Workers, enhancement, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox45 | --- | affected |
People
(Reporter: bkelly, Unassigned)
References
(Depends on 69 open bugs)
Details
(Keywords: meta)
Updated•8 years ago
|
Reporter | ||
Updated•8 years ago
|
Updated•7 years ago
|
Comment 1•5 years ago
|
||
I would assume, that this bug talks mostly about enhancements in terms of missing things rather than defects of existing implementations. This implies, that probably most if not all the blocking defects should change to be enhancements, too (or moved to a different meta bug). I will not do this now as bulk operation but we should look at each bug separately.
Comment 2•5 years ago
|
||
:asuth, can we break this into specific, finite, shippable things?
Comment 3•5 years ago
|
||
(In reply to Jens Stutte [:jstutte] from comment #2)
:asuth, can we break this into specific, finite, shippable things?
This is a type-4 meta bug in your classification system; it's just for tracking/linking spec-related issues. It helps us and other browser vendors answer the question "in what ways does Firefox deviate from the spec" and helps us answer "how do we fix our deviations". The ServiceWorker spec is a living standard that we expect to continually evolve over time. There is no endpoint[1], so it's not clear it would ever make sense to close the bug, although maybe one might move some of the resolved dependencies to some type of archival bug so the bugzilla UI doesn't freak out. (Creating successor meta bugs is possible, but is bad from a URL perspective, as anyone following old links then has to spend extra time figuring out what the successors are.)
1: For patent/IPR reasons, there are versioned releases of the ServiceWorker spec because the living spec doesn't get the legal protections. But we only implement against the living spec. There's an effort to try and make the whole process at the W3C lighter-weight.
Updated•2 years ago
|
Description
•