- From: Amelia Bellamy-Royds via GitHub <sysbot+gh@w3.org>
- Date: Fri, 19 Aug 2016 22:32:49 +0000
- To: public-svg-issues@w3.org
AmeliaBR has just labeled an issue for https://github.com/w3c/svgwg as "SVG Core": == Require HTML 5 parser to correctly parse embedded HTML elements == We currently have a warning at the end of in [the section on embedded HTML elements](https://www.w3.org/TR/2015/WD-SVG2-20150915/embedded.html#HTMLElements): > The HTML5 elements in the HTML namespace in an SVG subtree, itself nested in an HTML5 document, are not parsed by the HTML parser as HTML elements. In such case, the nested HTML elements should be created and inserted in the DOM using DOM APIs. I'm going to re-write that to be more readable, but I'm not sure why the requirement is there in the first place. What's the point of allowing these elements within SVG subtrees if they aren't going to be correctly parsed in inline SVG? The HTML parser already correctly parses and namespaces HTML elements inside of SVG `<title>` and `<desc>` (even though they has no useful purpose). It also automatically switches to the HTML namespace for descendents of `<foreignObject>`. ([Quick demo of the different cases](http://jsbin.com/jiwoferuce/2/edit?html,js,console,output)) Why can't it do the same for `<iframe>`, `<canvas>`, `<audio>`, `<video>`, and their descendents? Was this discussed with any HTML spec authors or browser implementers, or did someone just test and see that current browsers parse these as unknown SVG elements, and specced it from there? See https://github.com/w3c/svgwg/issues/240
Received on Friday, 19 August 2016 22:33:21 UTC