Looks like they're on their way to piece-mealy rediscover SGML, with config options to exclude non-permissible elements and attributes such as <script> and oncl

Looks like they're on their way to piece-mealy rediscover SGML, with config options to exclude non-permissible elements and attributes such as <script> and onclick. Except SGML can do this in a holistic, context-dependent way which brings us to > Issue 1: It’s unclear whether we can assume a generic context for parseFromString, or if we need to re-work the API to take the insertion context of the created fragment into account. which of course refers to the concept of tag inference/omission in HTML/SGML not covered in this proposal at all, and similarly > Issue 2: What about comment nodes, CDATA, etc. ? and > Some HTML elements require special treatment in a way that can’t be easily expressed in terms of configuration options or other algorithms. The following algorithm collects these in one place: To handle "funky elements" on a given element, run these steps: ... (introducing the ad-hoc concept of funky elements), and > Issue 3: The spec currently treats MathML and SVG as unknown content and therefore blocked by default. This needs to be fixed. It's depressing that we're iterating over these kind of issues that seemed like a solved problem in 1986 (35 years ago) when SGML was first published.