[whatwg/dom] Revamp the way DOM talks about nodes (#1004)

1. Address numerous xref issues around the term node and prevent some from occurring for the term children.
2. Embrace Attr as a node even more.
3. Rely on Web IDL's implements and interface primitives to reduce the opportunities for confusion.

Fixes https://github.com/heycam/webidl/issues/659, #597, #636, and #719.

<!--
Thank you for contributing to the DOM Standard! Please describe the change you are making and complete the checklist below if your change is not editorial.
-->

- [ ] At least two implementers are interested (and none opposed):
   * …
   * …
- [ ] [Tests](https://github.com/web-platform-tests/wpt) are written and can be reviewed and commented upon at:
   * …
- [ ] [Implementation bugs](https://github.com/whatwg/meta/blob/main/MAINTAINERS.md#handling-pull-requests) are filed:
   * Chrome: …
   * Firefox: …
   * Safari: …

I'll keep this template for now as we might want to test some aspects around `Attr` nodes, e.g., `attr.isConnected`, though I wasn't able to spot any weirdness between implementations thus far.

(See [WHATWG Working Mode: Changes](https://whatwg.org/working-mode#changes) for more details.)

You can view, comment on, or merge this pull request online at:

  https://github.com/whatwg/dom/pull/1004


-- Commit Summary --

  * Revamp the way DOM talks about nodes

-- File Changes --

    M dom.bs (437)

-- Patch Links --

https://github.com/whatwg/dom/pull/1004.patch

https://github.com/whatwg/dom/pull/1004.diff


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/dom/pull/1004