Re: More on SVG within HTML pages

Tab Atkins Jr. wrote:
> On Tue, Sep 8, 2009 at 12:25 PM, Shelley Powers<> wrote:
>> Frankly, I'm not sure what the concerns are about this anymore. I've heard
>> copy and paste, but copy and paste errors will cause the SVG to fail anyway.
> Coming into this late, and don't generally have anything intelligent
> to add, but I *can* add that there is more to the copy and paste issue
> than you suggest here.
> The real issue is not that copy and paste errors will cause the SVG to
> fail.  As you correctly say, that's true today.  The issue is that
> copy and paste errors *today* result in the page ignoring the SVG in
> some manner (possibly requiring the page author to hack around the
> broken markup, because they don't understand what's wrong and think
> that the browser is being stupid).  If not handled correctly, though,
> those same errors tomorrow (in an HTML5 browser) will result in the
> page itself being broken, possibly in a major way.
> ~TJ
And that is a valid concern.  I don't think it will be a really 
pervasive problem. I really don't think we're going to see this as a 
major point of failure when it comes to SVG, HTML5, or both. I do 
understand the concern, though.

But the bug I submitted, and my original email on the topic had to do 
with namespaced entities in the SVG. Not copy and pasting SVG.

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 


Received on Tuesday, 8 September 2009 19:24:52 UTC