- From: Ben Boyle <benjamins.boyle@gmail.com>
- Date: Sun, 16 Mar 2008 01:16:31 +1000
- To: "Henri Sivonen" <hsivonen@iki.fi>
- Cc: "Doug Schepers" <schepers@w3.org>, "HTMLWG Tracking WG" <public-html@w3.org>
On Sun, Mar 16, 2008 at 1:01 AM, Henri Sivonen <hsivonen@iki.fi> wrote: > On Mar 15, 2008, at 15:58, Doug Schepers wrote: > > So, with the following snippet: > > > > <svg xmlns="http://www.w3.org/2000/svg"> > > <circle cx="100" cy="50" r="25" fill=red stroke="blue" /> > > <circle cx="100" cy="50" r="15" fill="yellow" stroke="blue" /> > > </svg> > > > > You would see a yellow circle with a blue stroke on top of a black > > circle with no stroke. That's well defined, and not particularly > > draconian. And it's easy to understand. > > How is that more useful that having the first circle filled red and > stroked blue? I agree with Doug. Scenario: I am using text/html. You've sold me on not deploying web content as xhtml. I've embedded that html snippet, and I've made that error in the code. Unlike me to forget quotes of all things, but there you go. I'm seeing the red circle stroked blue, it's all cool. Suddenly I am enlightened that I should use an SVG file and link to it, rather than embed and serve this same snippet of SVG on every page. I dutifully move the SVG code into logo.svg, link it with an img tag and... what the? The circle went black! These things are authoring nightmares. Just don't do it. Consistency please! > How is that worth the complexity of having two different attribute > tokenization rules that get toggled in mid-parse? It's funny (ironic) you say that, because from my point of view you are proposing the complexity of two different attribute tokenization rules that get toggled depending on the source serialisation. We must be from different worlds ~:)
Received on Saturday, 15 March 2008 15:17:12 UTC