Editorial: explain the possible primary interfaces for nodes

[domenic]

I was trying to check whether a switch statement was exhaustive and had to do a bit of mental juggling to get there. I thought I'd write out the results for future reference.

---

Preview | Diff

[annevk]

Suggested change

	{{Document}}, {{DocumentFragment}}, {{DocumentType}}, {{Element}} or an inherited interface of it,
	{{Document}}, {{DocumentFragment}}, {{DocumentType}}, or {{Element}}; or an inherited interface of it:

[annevk]

Although I'm not sure how this is correct. Why is ProcessingInstruction an inherited interface and Comment is not?

Also, why would ShadowRoot not be a primary interface? Isn't that the most derived? And I think both Text and CDATASection are primary interfaces as they are the most derived on the objects they occur on. Just when CDATASection is the primary interface, it's also an inherited interface of Text.

[domenic]

The suggested change seems incorrect, and then your further comment seems to be based on confusion about what the spec text would say after that incorrect change.

I'll rephrase the original in another way. Every node's primary interface is one of:

• Attr
• CDATASection
• Comment
• Document
• DocumentFragment
• DocumentType
• Element
• HTMLElement
• HTMLHtmlElement
• ...
• ProcessingInstruction
• ShadowRoot
• Text

[annevk]

I see, that makes sense. Can we put them in the same order as the document outline does? I think I generally try to be consistent about that node order throughout the document.

[domenic]

Done!