- From: Elliott Sprehn <esprehn@chromium.org>
- Date: Thu, 7 May 2015 14:11:18 -0700
- To: Boris Zbarsky <bzbarsky@mit.edu>
- Cc: WHATWG <whatwg@lists.whatwg.org>, "Tab Atkins Jr." <jackalmage@gmail.com>, Rune Lillesveen <rune@opera.com>
On Thu, May 7, 2015 at 2:09 PM, Boris Zbarsky <bzbarsky@mit.edu> wrote: > On 5/7/15 5:07 PM, Tab Atkins Jr. wrote: > >> I believe the SVGWG is fine with a parsing-based approach, exactly >> like what HTML does. An SVG element created with mixed casing, or >> imported from an XML document, might not match a lowercase tagname >> selector, but SVG written in HTML will. >> > > Hmm. The main problem here is for scripts that create SVG elements in an > HTML document, since those have to use createElementNS and pass the > mixed-case names (e.g. for foreignObject). One idea could be to make createElement() return SVG elements for svg tag names embedded in HTML. Neither spec is ever going to have a conflicting tag name. - E
Received on Thursday, 7 May 2015 21:12:24 UTC