- From: Anne van Kesteren <annevk@opera.com>
- Date: Fri, 11 Nov 2011 10:49:55 +0100
- To: "Simon Pieters" <simonp@opera.com>, "Jonas Sicking" <jonas@sicking.cc>
- Cc: "Henri Sivonen" <hsivonen@iki.fi>, "public-webapps WG" <public-webapps@w3.org>
On Fri, 11 Nov 2011 10:44:10 +0100, Jonas Sicking <jonas@sicking.cc> wrote: > For all element names defined in SVG 1.1 (for now), make the parser > treat it just as it would have if it had parsed "<svg><g>...", except > that it obviously wouldn't output the <svg> element. > > There are a few tags where this is a big problem. At least for <a>, > <script> and <style> appear both in SVG and HTML and so for markup > like "<a>...", "<style>..." and "<script>..." we don't know which > namespace to create the element in. Fortunately these elements behave > mostly the same no matter which namespace they are created in. Not if you have "<a><g>". > Unfortunately <style> and <script> are parsed differently depending on > if they live in foreign content or not. However this is something we > can fix, and would lead to a lot of other benefits (such as scripts > parsed consistently when moved around in the markup). I do agree it would make sense to parse these consistently throughout text/html. -- Anne van Kesteren http://annevankesteren.nl/
Received on Friday, 11 November 2011 09:50:41 UTC