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

Re: Some notes on SVG parsing in HTML 5

From: Erik Dahlstrom <ed@opera.com>
Date: Wed, 18 Feb 2009 09:46:48 +1100
To: "Cameron McCormack" <cam@mcc.id.au>, public-svg-wg@w3.org
Message-ID: <op.upipkaiigeuyw5@macbooked.local>
On Tue, 17 Feb 2009 23:23:56 +1100, Cameron McCormack <cam@mcc.id.au> wrote:


> Parsing:
>   <!DOCTYPE html>
>   <html>
>     <head>
>       <title></title>
>     </head>
>     <body>
>       <svg xmlns='http://www.w3.org/2000/svg'>
>         <a xlink:href='somewhere'/>
>       </svg>
>     </body>
>   </html>
> would be conforming, despite not having an xmlns:xlink="" declaration in
> scope.

If that's the case, one might even wonder why not simply use "href" as the attribute name, if this auto-qualification happens. It would hurt compatibility with xhtml+svg possibly, but you'd still need to change the document.

> Having on an SVG element an xmlns:xlink="" attribute whose value isn't
> the XLink namespace makes the document non-conforming.
> Including:
>   <SVG XMLNS='http://www.w3.org/2000/svg'>
>     <AniMatemotion/>
>   </svg>
> in an appropriate place is conforming, despite the case differences in
> the element and attribute names.  Further, these attribute and element
> names are mapped to the appropriate case when the element/attribute is
> created.  So the above is equivalent to:
>   <svg xmlns='http://www.w3.org/2000/svg'>
>     <animateMotion/>
>   </svg>

Going from html to xhtml you would hit the same issue though, that casing would have to be corrected if it wasn't proper in the html source.

> Any element names that aren't recognised as SVG or HTML ones will be
> created as plain Element objects (I think). 

Are you sure it's not HTMLElement rather than Element?

> Any such elements, or
> attributes that aren't recognised as one of the SVG attributes that
> is not all lowercase, will be case folded to lowercase. Thus:
>   <svg xmlns='http://www.w3.org/2000/svg'>
>     <g myCustomAttribute='abc'/>
>   </svg>
> will be parsed as:
>   <svg xmlns='http://www.w3.org/2000/svg'>
>     <g mycustomattribute='abc'/>
>   </svg>

That could be a problem, though the fact that most custom content/attributes in svg uses namespaces that's not the only problem you're likely to encounter.

> No foreign content elements imply any start or end tags.

Ok, that's good I think.

> XML-style CDATA sections are supported.


> A <!DOCTYPE> in an SVG fragment will make the document non-conforming,
> as will an XML declaration.

In xhtml+svg the same would happen right?

> SVG Tiny 1.2 elements aren't considered, and so <textArea> will parse
> as an HTML <textarea> element and break out of foreign content mode.
> <font> is recognised as an <svg:font> element when in foreign content
> mode, however.  I have checked that all mixed case SVG 1.1 element names
> are in the HTML 5 table of case mappings.  (I haven't checked the list
> of attribute case mappings.)

There are a few different ways we could deal with that. Leaving that for the discussion.

> Prefixed SVG elements cannot be used, and prefixes other than xlink
> cannot be used for the XLink attributes.  xml:base and friends will
> parse in the same way.

I think it would probably be acceptable to me to not have the option of prefixed svg (or otherwise) elements in html. Most tools don't output prefixed elements anyway AFAIK, and IMHO prefixes makes content less readable.

> 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.

So we should perhaps ask the HTML WG (or the editor) about that.

> Inside a <foreignObject>, <desc> or <title> element, direct child
> elements will be parsed as if they weren’t in a foreign content context.
> So for example, a <font> child of <title> will become an HTML <font>,
> and a <rect> child would be parsed as an element
> {http://www.w3.org/1999/xhtml}rect, but an <svg> child would be parsed
> as a {http://www.w3.org/2000/svg}svg again.

Though you could open another foreign content context by <foreignObject><mathml...> yes?

> In foreign content mode, a <font> start tag with a color, face or size
> attribute will cause the document to be non-conforming.  <!-- the
> attributes here are required so that SVG <font> will go through as SVG
> but legacy <font>s won't -->  I'll note that color is a valid attribute
> to use on <font> in SVG (being the presentation attribute for the color
> property), but that it would be extremely uncommon, although not without
> some effect: arbitrary content glyphs could be using currentColor as
> fill/stroke on some shapes, which thus reference the color property set
> on the <font>.

Not a big problem I think.

> The following start tags cause a parse error inside foreign content:
> b, big, blockquote, body, br, center, code, dd, div, dl, dt, em, embed,
> h1, h2, h3, h4, h5, h6, head, hr, i, img, li, listing, menu, meta, nobr,
> ol, p, pre, ruby, s, small, span, string, strike, sub, sup, tbale, tt,
> u, ul and var.  <!-- this list was determined empirically by studying
> over 6,000,000,000 pages that were specifically not XML pages -->

No conflicts there I think, though one thought would be whether or not it would be useful to have known HTML elements parsed and inserted as HTML elements even when inside an svg fragment like this one:

<svg xmlns...>
  <link rel="stylesheet" .../>

In xhtml you'd put a prefix on the link element, and in general you could put non-svg elements whereever you wanted as long as the corresponding prefix was defined.

> Any SVG element can use the self-closing <syntax/>.


> All of the character references that can be used in PCDATA and RCDATA
> sections can be used in foreign content, too.

Makes sense.

> All of the attribute syntaxes allowed on HTML elements (double quoted,
> single quoted, unquoted and minimized) are allowed on foreign content.
> Various other kinds of invalid syntax which causes a parse error but
> still parses will behave the same in foreign content (such as correction
> of mis-nested open/close tags).

Ok, leaving those two for the discussion.


Erik Dahlstrom, Core Technology Developer, Opera Software
Co-Chair, W3C SVG Working Group
Personal blog: http://my.opera.com/macdev_ed
Received on Tuesday, 17 February 2009 22:47:57 UTC

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