Re: [webcomponents] Should parser extensibility be a design goal? (#113)

My take:

- It would be great from an "explaining the platform" point of view.
- Void elements are very convenient. I would like custom void elements.
- Parsing rules that restrict content to only certain other content, and push other content out (like `<table>`), seem kind of nice. (But also kind of horrible?)
- On the other hand, the parser is basically a giant pile of accidental complexity. Do we really want to make it hookable? Maybe "explaining the parser" be more like "explaining sync XHR"---a bad idea, even if we theoretically could.

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/113#issuecomment-111530841