W3C home > Mailing lists > Public > public-html@w3.org > March 2008

Re: SVG and MathML in text/html

From: Ben Boyle <benjamins.boyle@gmail.com>
Date: Sun, 16 Mar 2008 02:36:39 +1000
Message-ID: <5f37426b0803150936n532b8ae6i592ea1ec3b3b4fd6@mail.gmail.com>
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:43 AM, Henri Sivonen <hsivonen@iki.fi> wrote:
> On Mar 15, 2008, at 17:16, Ben Boyle wrote:
>
>  > 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!
>
>  Nope, you get the YSoD.

I wondered about that!

Now, do I really get the yellow screen of death?
I have a text/html document. It is valid and conforming. It has <img
src="logo.svg">
logo.svg is, as above, not well-formed.

I should see my HTML page. The page is OK. The image will be broken.

I want the same result with inline SVG. The HTML page rendered with a
broken image.

I do not want draconian error handling applied to HTML! (This in reply
to Geoffrey too) I don't even like it applied to XHTML (in web
browsers) but ya'll already implemented that :P You can fix it any
day. I don't even need a button to toggle it on/off, because there are
already tools that tell me whether the pages are valid or not (without
YSoD). Web pages are supposed to recover from errors gracefully and in
the best interests of the user, why did browser vendors forget this? I
digress ...

You want to make a best effort to render SVG, even broken SVG. You
know, I'm not against that. It's how XHTML should be handled (in the
browser, for the end-user). If you are going to render *something*
when that SVG is embedded in the page, then yes the red circle with
blue stroke is the obvious intent of the author. Can you render the
same when that SVG is placed in logo.svg and loaded in via <img>, for
all the same reasons (what users wants to see a broken image? none!),
and for the sake of consistency.

Can you/we (this WG) then influence the SVG group to endorse this
rendering for SVG in all contexts? That is the holy grail for me. I
have my doubts about it happening, but unless it does there will be
incompatibility to be dealt with. I'm asking if we can avoid that.
Just asking! (Going to keep asking though :)

In a nutshell: I deal with markup. I don't want it to mean something
different (if we can help it), whether its placed within the HTML or
linked.
Received on Saturday, 15 March 2008 16:37:17 GMT

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