moving getSVGDocument to the HTML spec from Cameron McCormack on 2014-06-05 (public-svg-wg@w3.org from April to June 2014)

From: Cameron McCormack <cam@mcc.id.au>
Date: Thu, 05 Jun 2014 22:31:28 +1000
To: public-svg-wg@w3.org
Message-ID: <53906320.5010104@mcc.id.au>

The getSVGDocument method, which we've marked as deprecated, is now 
defined to be an alias for contentDocument.  In this thread 
http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2013-November/253271.html 
and this bug https://www.w3.org/Bugs/Public/show_bug.cgi?id=25940 some 
people mentioned that it would be easier if this was defined in HTML 
alongside the definition of contentDocument itself.  We would need to 
copy the more detailed wording about browsing contexts etc. if we kept 
it in SVG.

Are there any objections to moving it to the HTML spec?  I don't think 
there is any particular advantage to keeping this wart in the SVG spec.

Received on Thursday, 5 June 2014 12:31:46 UTC