W3C home > Mailing lists > Public > public-svg-wg@w3.org > January to March 2009

[Fwd: Re: Some notes on SVG parsing in HTML 5]

From: Doug Schepers <schepers@w3.org>
Date: Thu, 26 Feb 2009 08:13:34 -0500
Message-ID: <49A6957E.6040905@w3.org>
To: SVG WG <public-svg-wg@w3.org>

-------- Original Message --------
From: Henri Sivonen <hsivonen@iki.fi>
To: Simon Pieters <simonp@opera.com>

On Feb 26, 2009, at 02:04, Simon Pieters wrote:

>>> Parsing this document:
>>>  <!DOCTYPE html>
>>>  <html>
>>>    <head>
>>>      <title></title>
>>>    </head>
>>>    <body>
>>>      <svg>
>>>        <circle r='100'/>
>>>      </svg>
>>>    </body>
>>>  </html>
>>> would be non-conforming, since the <svg> tag is missing an
>>> xmlns='http://www.w3.org/2000/svg' attribute.
>> No, xmlns is optional. If it is preset, it must have the right
>> value, though.

BTW, what gives a *parser-level* error can be experimented with using 
  and how things might work in a browser can be experimented with
builds from 

  (these builds have issues with nested scripts, so don't try that ;-).

>>> There's a comment <!--XXXSVG need to define processing for </
>>> script> to
>>> match HTML5's </script> processing --> but I'm not sure what
>>> processing
>>> this means.
>> See: http://www.whatwg.org/specs/web-apps/current-work/multipage/tree-construction.html#parsing-main-incdata
>> Basically, it says how to run the script in a way that is
>> compatible with how browsers have to do it for HTML (in the face
>> of, say, an external script that document.writes another external
>> script that document.writes something).

I've implemented things in such a way that SVG </script> triggers
execution in exactly the same way as HTML </script>.

Henri Sivonen

-Doug Schepers
W3C Team Contact, SVG and WebApps WGs
Received on Thursday, 26 February 2009 13:13:43 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:29:41 UTC