- From: Amelia Bellamy-Royds via GitHub <sysbot+gh@w3.org>
- Date: Sat, 20 Aug 2016 05:43:22 +0000
- To: public-svg-issues@w3.org
Thanks @fsoder. Thanks for those links; I hadn't gotten as far as really looking into how the parser treats the namespace switch currently. And unfortunately, it doesn't look like handling the embedded content elements would be as simple as adding new entries to the list of "HTML integration point" nodes, since those are nodes in the _current_ parser namespace (SVG or MathML) which trigger a switch to the HTML namespace for their descendents. Instead, there would need to be an extra step with a special whitelist of tag names added to the [rules for parsing foreign content](https://html.spec.whatwg.org/multipage/syntax.html#parsing-main-inforeign). Not impossible, but I certainly understand the reluctance to modify the HTML parser. On the SVG side, if the HTML working groups do _not_ support changing the parser, I really don't see what the point is in allowing these elements directly in the SVG fragment, instead of having them as children of `<foreignObject>`. -- GitHub Notification of comment by AmeliaBR Please view or discuss this issue at https://github.com/w3c/svgwg/issues/240#issuecomment-241181246 using your GitHub account
Received on Saturday, 20 August 2016 05:43:29 UTC