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).

Difference between revisions of "Fork tracking"

From WHATWG Wiki
Jump to navigation Jump to search
(Update for latest W3C-side redirects)
(webmessaging redirects)
 
Line 13: Line 13:
*** https://www.w3.org/TR/2dcontext/
*** https://www.w3.org/TR/2dcontext/
*** https://www.w3.org/TR/eventsource/
*** https://www.w3.org/TR/eventsource/
** 404s (should redirect)
*** https://www.w3.org/TR/webmessaging/


== Confusion mitigated ==
== Confusion mitigated ==
Line 28: Line 26:
*** https://www.w3.org/TR/websockets/
*** https://www.w3.org/TR/websockets/
*** https://www.w3.org/TR/2dcontext2/
*** https://www.w3.org/TR/2dcontext2/
*** https://www.w3.org/TR/webmessaging/
** The following ED URLs of HTML subsets redirect:
** The following ED URLs of HTML subsets redirect:
*** https://w3c.github.io/webmessaging/
*** https://w3c.github.io/webmessaging/

Latest revision as of 23:04, 26 August 2021

This page exists to document the status of the outdated forks of various WHATWG specifications, and any progress toward clarifying their out-of-dateness.

Per the Memorandum of Understanding between W3C and WHATWG, most of this should be cleared up, but it's not totally done.

Confusion persists with some mitigation

Confusion mitigated

Non-forks

Some work started out in W3C Working Groups or Community Groups but has since moved to the WHATWG. This section tracks what happened in those cases.