A user account is required in order to edit this wiki, but we've had to disable public user registrations due to spam.
To request an account, ask an autoconfirmed user on Chat (such as one of these permanent autoconfirmed members).
Fork tracking: Difference between revisions
Jump to navigation
Jump to search
(→Confusion Persists: add CORS) |
No edit summary |
||
| Line 35: | Line 35: | ||
** http://www.w3.org/TR/XMLHttpRequest2/ | ** http://www.w3.org/TR/XMLHttpRequest2/ | ||
** Status: Although XHR "level 2" has been discontinued as a NOTE, XHR "level 1" continues to exist as an outdated snapshot with no warning, causing confusion. The spec is not properly layered on top of the Fetch Standard, either, which means it fails to integrate with the rest of the platform (e.g. it is not intercepted by service workers). | ** Status: Although XHR "level 2" has been discontinued as a NOTE, XHR "level 1" continues to exist as an outdated snapshot with no warning, causing confusion. The spec is not properly layered on top of the Fetch Standard, either, which means it fails to integrate with the rest of the platform (e.g. it is not intercepted by service workers). | ||
Revision as of 08:45, 25 September 2015
This page exists to document the status of the outdated forks of various WHATWG specifications, and any progress toward clarifying their out-of-dateness.
Confusion Mitigated
- Fullscreen
- http://www.w3.org/TR/fullscreen/
- Status: discontinued as a NOTE. ED URL (http://dvcs.w3.org/hg/fullscreen/raw-file/tip/Overview.html) redirects
Confusion Somewhat Mitigated
- URL
- http://www.w3.org/TR/url/ plus various aliases and older versions
- Status: has a reasonable red disclaimer, but still exists.
- Streams
- http://www.w3.org/TR/streams-api/
- Status: mostly gutted, with a reasonable red disclaimer.
Confusion Persists
- CORS
- http://www.w3.org/TR/cors/
- Status: still exists as an outdated specification with no warning, causing confusion. Obsoleted by the Fetch standard.
- DOM
- http://www.w3.org/TR/dom/
- Status: still exists as an outdated snapshot with no warning, causing confusion. And has a weird rename too.
- Encoding
- http://www.w3.org/TR/encoding/
- Status: still exists as an outdated snapshot with no warning, causing confusion
- Notifications
- http://www.w3.org/TR/notifications/
- Status: still exists as an outdated snapshot with no warning, causing confusion. The spec model has diverged significantly in the meantime, and the outdated version is actively wrong, not just incomplete.
- XMLHttpRequest
- http://www.w3.org/TR/XMLHttpRequest/
- http://www.w3.org/TR/XMLHttpRequest2/
- Status: Although XHR "level 2" has been discontinued as a NOTE, XHR "level 1" continues to exist as an outdated snapshot with no warning, causing confusion. The spec is not properly layered on top of the Fetch Standard, either, which means it fails to integrate with the rest of the platform (e.g. it is not intercepted by service workers).