W3C home > Mailing lists > Public > public-html@w3.org > September 2009

Re: More on SVG within HTML pages

From: Shelley Powers <shelleyp@burningbird.net>
Date: Tue, 08 Sep 2009 14:46:40 -0500
Message-ID: <4AA6B4A0.5060609@burningbird.net>
To: "Tab Atkins Jr." <jackalmage@gmail.com>
CC: public-html@w3.org, Lachlan Hunt <lachlan.hunt@lachy.id.au>
Tab Atkins Jr. wrote:
> On Tue, Sep 8, 2009 at 2:24 PM, Shelley Powers<shelleyp@burningbird.net> wrote:
>   
>> I'm assuming we've already worked through the issues related to the
>> possibility of mangled SVG in pages today, causing problems when accessed by
>> a HTMl5 browser tomorrow. I don't think that the namespaced entities will
>> add to this burden. In particular, those embedded by a tool like Inkscape
>> are so infused within the SVG that it becomes extremely difficult to remove.
>> In fact, trying to remove them manually will result in the errors that
>> people are most worried about.
>>
>> So my response is yes, I understand the concern. But the concern isn't
>> specific to the topic in this thread. Unless I'm misunderstanding the
>> concern?
>>     
>
> >From what I've gathered, part of the problem is that the 'easy'
> solutions to dealing with this (parse SVG like XML, frex) will make
> those sorts of copy and paste errors worse.  So any solution to the
> problem has to be more subtle.
>
> ~TJ
>
>   
Confused here.

Wasn't all of this discussed previously, when exchanges about allowing 
SVG in HTML first arose?

Right now, the namespaced entities are parsed as HTML, or at least 
that's how they are appearing in the DOM with the Firefox nightly I 
used. A little disappointing, but that wasn't an issue to me. Once JS 
developers are aware of the issue, we'll work around it, as we have 
worked around other differences in the past. And frankly, if JS 
developers are going to access anything in the SVG, it's the SVG 
objects, not the namespaced entities.

(Of course, if the SVG objects are namespaced, then the issue becomes 
more acute. But that rarely happens when copying from an external SVG file.)

The real issue that triggered me to start this thread was the enormous 
number of truly intimidating errors and warnings that the validator.nu 
provides. According to Henri, that's because he's following the spec. 
Hence, I filed a bug about the spec, specific to the impacted section.

One solution I didn't think we were going to go for was to parse the SVG 
as XML when it was in HTML. I thought that was a dead in the water 
concept from the start.

Shelley
Received on Tuesday, 8 September 2009 19:47:24 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:16:48 GMT