W3C home > Mailing lists > Public > www-svg@w3.org > October 2005

Re: [svg11] svg out-of-context rendering

From: Cameron McCormack <cam-www-svg@aka.mcc.id.au>
Date: Mon, 31 Oct 2005 19:39:52 +1100
To: www-svg@w3.org
Message-ID: <20051031083952.GD28891@port.mcc.id.au>

Anne van Kesteren:
> All nice about conforming documents and such. I suspected that. What I was
> asking about is what the rendering story is. "should get nothing" and "isn't
> good for rendering" are not exactly terms that lead to interoperable "error
> handling". Opera has two rendering stories at the moment, depending on which
> version you use and Mozilla has another that differs from both.

Then I guess according to the Error Processing section[1], which says:

   The document shall be rendered up to, but not including, the first
   element which has an error.
since the document element is the one causing it to be not a conforming
stand-alone document/fragment, nothing will be rendered.  Though perhaps
you could consider that element as being not the one that has an error,
but in fact it's the structure of the document that is causing the
problem, in which case that rule doesn't apply.  Seems reasonable that
it is, though.

In terms of a "CSS rendering context", as mentioned in the document's
comment, I don't think it's up to SVG to say how that works or when the
UA is meant to switch to this rendering mode.

[1] http://www.w3.org/TR/SVG11/implnote.html#ErrorProcessing

  e-mail : cam (at) mcc.id.au    	icq : 26955922
     web : http://mcc.id.au/	        msn : cam-msn (at) aka.mcc.id.au
  office : +61399055779		     jabber : heycam (at) jabber.org
Received on Monday, 31 October 2005 08:40:02 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 March 2017 09:47:04 UTC