W3C home > Mailing lists > Public > www-svg@w3.org > February 2008

Re: getSVGDocument()

From: Anne van Kesteren <annevk@opera.com>
Date: Fri, 15 Feb 2008 10:56:41 +0100
To: "Oliver Hunt" <oliver@apple.com>, anthony.grasso@cisra.canon.com.au
Cc: www-svg@w3.org
Message-ID: <op.t6j8krj864w2qv@annevk-t60.oslo.opera.com>

On Fri, 15 Feb 2008 08:05:52 +0100, Oliver Hunt <oliver@apple.com> wrote:
> I think Anne is asking if GetSVGDocument could be marked as an alias to  
> contentDocument (and maybe deprecated?).

Yeah!


> I'm going to step out on a limb and suggest Anne may be concerned about  
> the Acid3 SVG tests requiring a text/xml document to produce an  
> SVGDocument (and hence provide GetSVGDocument), which for various  
> reasons is non-trivial in a general purpose UA.  This is an issue that  
> WebKit also has -- the type of document created is determined by the  
> mime/type -- if it was determined by content then the type of a document  
> would need to be dynamic to allow for the user replacing the content of  
> (for example) n html document with the content of an SVG document.

This was not my specific concern as it seems the only case that didn't  
work for us was <iframe> because we hadn't implemented it on <iframe> (and  
also not on <frame>, but that's not tested).

Mostly I don't think we need getSVGDocument() at all, but apparently  
there's some content using it so the simplest solution seems to make it an  
alias for contentDocument (and maybe deprecate it, indeed, although if  
that doesn't lead to removal in the future I'm not sure if it's worth it).


-- 
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
Received on Friday, 15 February 2008 09:52:46 GMT

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