W3C home > Mailing lists > Public > www-svg@w3.org > August 2012

Re: GetSVGDocument interface

From: Erik Dahlstrom <ed@opera.com>
Date: Tue, 21 Aug 2012 09:27:22 +0200
To: www-svg@w3.org
Message-ID: <op.wjdqzwtegeuyw5@gnorps>
On Tue, 21 Aug 2012 06:54:09 +0200, Cameron McCormack <cam@mcc.id.au>  
wrote:

> Do we need to keep this interface, which has the getSVGDocument() method  
> on it, and which was intended to be implemented on interface like  
> HTMLObjectElement?  It's entirely redundant with contentDocument. Unless  
> people think content is using it, we should drop it.

http://stackoverflow.com/search?q=getSVGDocument hints that there is some  
usage, but the interface is marked as being deprecated in SVG 1.1 Second  
Edition [1]. I think in particular for embed elements there were browser  
inconsistencies with contentDocument (in the past at least) that may have  
pushed people towards using getSVGDocument.

Anyway, I think we should remove getSVGDocument from SVG2.


[1] http://www.w3.org/TR/SVG11/struct.html#InterfaceGetSVGDocument

-- 
Erik Dahlstrom, Core Technology Developer, Opera Software
Co-Chair, W3C SVG Working Group
Personal blog: http://my.opera.com/macdev_ed
Received on Tuesday, 21 August 2012 07:28:01 GMT

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