- From: Ryosuke Niwa <rniwa@apple.com>
- Date: Thu, 12 Mar 2015 07:57:29 -0700
- To: Robin Berjon <robin@w3.org>
- Cc: Anne van Kesteren <annevk@annevk.nl>, Benjamin Lesh <blesh@netflix.com>, WebApps WG <public-webapps@w3.org>
> On Mar 12, 2015, at 4:13 AM, Robin Berjon <robin@w3.org> wrote: > >> On 12/03/2015 11:07 , Anne van Kesteren wrote: >>> On Thu, Mar 12, 2015 at 4:32 AM, Benjamin Lesh <blesh@netflix.com> wrote: >>> What are your thoughts on this idea? >> >> I think it would be more natural (HTML-parser-wise) if we >> special-cased SVG elements, similar to how e.g. table elements are >> special-cased today. A lot of <template>-parsing logic is set up so >> that things work without special effort. By special casing, do you mean to recognize SVG element names? I'd prefer allowing template elements inside SVG as in: <svg><template>~</template></svg> > Or even go the extra mile and just slurp all SVG elements into the HTML namespace. There are a few name clashes, but we ought to be able to iron those out. I don't think we can make that change without breaking backwards compatibility. - R. Niwa
Received on Thursday, 12 March 2015 14:58:21 UTC