-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Figure out how to manage normative dependencies to WHATWG HTML for features not in W3C HTML for CR/REC #9
Comments
I'll be sending out a new CfC shortly. It would be helpful to get this hammered out for the ~3 references I need from WHATWG's HTML. :) |
Ping. I'm very wary of referencing W3C's "HTML 5.1" in its current state. If we'd like to move this document to CR, clarity on these kinds of dependencies would be appreciated. |
Somewhere public, I hope? |
@annevk likely public-webappsec |
@wseltzer: Sorry for the substantial delay; I got distracted. The CR proposed at https://lists.w3.org/Archives/Public/public-webappsec/2016Jul/0032.html mostly points to HTML 5.1 (though I haven't reviewed the diff from the WHATWG document, and as I noted in the F2F, I don't actually intend to do so), and has a few normative references to WHATWG specs in places where the W3C versions are missing concepts:
Note also that WEBWORKERS hasn't been updated since last September, and I haven't reviewed the diff to https://html.spec.whatwg.org/multipage/workers.html. I know that the WHATWG document is wildly divergent at this point, as the whole loading infrastructure has shifted. It would be lovely if there was a plan for removing or updating that document. |
Ping. :) |
another ping. |
I think HTML picked up the pieces I need. W3C's Workers spec still has one outstanding issue (w3c/workers#6). Again, I haven't reviewed any of that text for differences from the WHATWG doc; I've only verified that there's a valid link target with a reasonable name. |
This is a solved problem these days. |
No description provided.
The text was updated successfully, but these errors were encountered: