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

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

From: Jon Ferraiolo <jonf@adobe.com>
Date: Mon, 31 Oct 2005 00:39:18 -0800
Message-ID: <6ECA24BE410D994496A2AE995367C5C830177E@namail3.corp.adobe.com>
To: "Anne van Kesteren" <fora@annevankesteren.nl>, <www-svg@w3.org>

I suggest that SVG UAs *SHOULD* (MUST?) generate an error message when
encountering content which does not have a root 'svg' element
surrounding the content. 

In this particular example, the file extension was .xml, which means
that the file might never have been dispatched to an SVG UA. Instead,
some other UA might process the content, in which case the UA might
choose to just display an XML view of the content, for example.

-----Original Message-----
From: www-svg-request@w3.org [mailto:www-svg-request@w3.org] On Behalf
Of Anne van Kesteren
Sent: Monday, October 31, 2005 12:29 AM
To: www-svg@w3.org
Subject: Re: [svg11] svg out-of-context rendering


Quoting Cameron McCormack <cam-www-svg@aka.mcc.id.au>:
> If you are using an SVG UA to render that document, I think you should
> get nothing since it's not a Conforming SVG Stand-Alone File[1].  If
> you're using some other XML UA where SVG content is allowed (such as
> XHTML+SVG) then it's not a Conforming SVG Included Document
Fragment[2],
> so also isn't good for rendering.

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.

Kind regards,

Anne van Kesteren


-- 
Anne van Kesteren
<http://annevankesteren.nl/>
Received on Monday, 31 October 2005 08:39:45 GMT

This archive was generated by hypermail 2.3.1 : Friday, 8 March 2013 15:54:31 GMT