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

Self closing elements DO seem like a useful thing to have.  I don't think we want to make parsing behavior polymorphic as done for table and tr elements though.  It makes HTML parsing incompatible with XML parser, and all sorts of insanity ensues.  One way to mitigate this problem would be let any element that has `-` in its name appear anywhere template element could appear.

For script and style, I don't think we necessarily want the exact same parsing rule that takes care of `<!--`, `-->`, etc... since they're mostly historical artifacts.  For those use cases, we may want to allow contents to be parsed as CDATA.

Note that upgrading makes even less sense once we allow the parser behavior depend on element definition since we wouldn't know how to parse an element until the definition is available, and we certainly don't want to make the parsing rule racy.

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