Skip to content
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

Start using the Infra Standard #2053

Closed
7 of 16 tasks
domenic opened this issue Nov 16, 2016 · 1 comment
Closed
7 of 16 tasks

Start using the Infra Standard #2053

domenic opened this issue Nov 16, 2016 · 1 comment
Labels
clarification Standard could be clearer integration Better coordination across standards needed

Comments

@domenic
Copy link
Member

domenic commented Nov 16, 2016

See https://blog.whatwg.org/infra for background. Let's use this issue to track the changes we'll want to make to HTML. I anticipate us doing so over the course of several PRs, as the data structures especially might require some back and forth (e.g. adding missing things to Infra for manipulating them).

  • Overall integration
    • Add to the kitchen sink diagram, maybe? It's also missing Fetch, and is getting crowded.
    • Add a prominent "HTML depends on the Infra Standard" somewhere early; maybe in the beginning of 2. Common infrastructure, before 2.1. Terminology?
    • Add an appropriate section with dfn cross references to Dependencies; probably before anything else
  • Removal of now-redundant things
  • Data structure usage (not complete, update as we find more...)
    • module map
    • CustomElementRegistry (kind of a strange case)
    • when-defined promise map
    • custom element reaction queue
    • custom element reactions stack
    • element queue
    • backup element queue
domenic added a commit that referenced this issue Nov 16, 2016
This takes care of many of the easier parts of #2053.
annevk pushed a commit that referenced this issue Nov 17, 2016
This takes care of many of the easier parts of #2053.
annevk added a commit that referenced this issue Nov 18, 2016
Helps with #2053 as well as URL, DOM, etc. by avoiding the ambiguity of
multiple standards defining ASCII case-insensitive.

This also cleans up the remaining mentions of RFC2119.
domenic pushed a commit that referenced this issue Nov 18, 2016
Helps with #2053 as well as URL, DOM, etc. by avoiding the ambiguity of
multiple standards defining ASCII case-insensitive.

This also cleans up the remaining mentions of RFC2119.
@annevk annevk added integration Better coordination across standards needed clarification Standard could be clearer labels Jan 22, 2018
alice pushed a commit to alice/html that referenced this issue Jan 8, 2019
This takes care of many of the easier parts of whatwg#2053.
alice pushed a commit to alice/html that referenced this issue Jan 8, 2019
alice pushed a commit to alice/html that referenced this issue Jan 8, 2019
Helps with whatwg#2053 as well as URL, DOM, etc. by avoiding the ambiguity of
multiple standards defining ASCII case-insensitive.

This also cleans up the remaining mentions of RFC2119.
@domenic
Copy link
Member Author

domenic commented Mar 25, 2020

I'm happy with our current strategy of upgrading as we go; we don't need a separate tracking issue for this.

@domenic domenic closed this as completed Mar 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
clarification Standard could be clearer integration Better coordination across standards needed
Development

No branches or pull requests

2 participants