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 IRC (such as one of these permanent autoconfirmed members).

Difference between revisions of "Fork tracking"

From WHATWG Wiki
Jump to: navigation, search
(Confusion persists: webstorage ED has warning as well)
Line 22: Line 22:
 
** In general all of these attempt to copy-and-paste HTML and then apply forked patches on top, but the scripts are wonky, leading to lots of errors.
 
** In general all of these attempt to copy-and-paste HTML and then apply forked patches on top, but the scripts are wonky, leading to lots of errors.
 
** Subsets of HTML split out into other outdated forks, none with appropriate warnings:
 
** Subsets of HTML split out into other outdated forks, none with appropriate warnings:
*** http://www.w3.org/TR/webstorage/
+
*** http://www.w3.org/TR/webstorage/ (ED is nice at least https://w3c.github.io/webstorage/)
 
*** http://www.w3.org/TR/workers/
 
*** http://www.w3.org/TR/workers/
 
*** http://www.w3.org/TR/webmessaging/ (ED is nice at least https://w3c.github.io/webmessaging/)
 
*** http://www.w3.org/TR/webmessaging/ (ED is nice at least https://w3c.github.io/webmessaging/)

Revision as of 10:18, 27 January 2018

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 persists

Confusion persists with some mitigation


Confusion mitigated