W3C home > Mailing lists > Public > public-svg-wg@w3.org > October to December 2010

xlkink:href and getCoordAt update

From: Patrick Dengler <patd@microsoft.com>
Date: Thu, 14 Oct 2010 18:15:18 +0000
To: Erik Dahlstrom <ed@opera.com>, "public-svg-wg@w3.org" <public-svg-wg@w3.org>
Message-ID: <4A2DB3AE4504E944AF122BBFBA7FBA1F5402380C@TK5EX14MBXC118.redmond.corp.microsoft.com>
I wanted to give an update on two topics that came up at a previous teleconference.

Topic: href

We did a very deep review on the xlink:href/href specification.

http://www.w3.org/Graphics/SVG/WG/wiki/index.php?title=Href&amp;diff=1927&amp;oldid=prev

It appears that our first analysis surfaced that this would be big work item based upon the way it was specified, and that it wouldn't fit in our timeframe for IE9.  We do agree that this is an important specification to help web developers adopt SVG.  Upon closer investigation and many design sessions, we have identified the following change in the proposal which would make it much more palatable.

"When serialized, all attribute are retained as set in the original document"

Changed to:

"When serialized, all attribute are retained as described by the HTML specification."

If we make this change, case sensitive issues that were causing significant issues for us (and perhaps for others) disappear.
I will hopefully get back soon on whether or not this will be in IE9.

Topic: getCoordsAt(x,y)  
Doug and our representatives in the WebApps working group had further conversations on this topic.  It appears that the conclusion was that a method may not be properly designed to be attached to mouseevents.  A revised specification would help but it does not mean that it would make IE9.  However, I do think the feature idea is spot on. 
Received on Thursday, 14 October 2010 18:15:58 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 14 October 2010 18:15:59 GMT