Re: handling XLink deprecation

On Tuesday, August 21, 2012, 6:45:59 AM, Cameron wrote:

CM> I am not sure if we have resolved exactly how we will handle the XLink
CM> deprecation.  If we have, please feel free to remind me what we decided. :)

http://www.w3.org/Graphics/SVG/WG/wiki/Href

CM> But I propose we:

CM> * remove xlink:actuate, xlink:type, xlink:role, xlink:arcrole and 
CM> xlink:title altogether

Yes

CM> * change xlink:href to href for: <a>, <altGlyph>, the animation 
CM> elements, <color-profile>, <filter>, <font-face-uri>, <glyphRef>, 
CM> gradient elements, <mpath>, <pattern>, <textPath>, <tref> and <use>

Yes (I already made that change for color-profile yesterday. Note though that @color-profile uses src; maybe color-profile should as well).

CM> * change xlink:href to src for: <cursor>, <feImage>, <image> and <script>

yes

CM> * change xlink:show to target on <a>, and not allow it on any other element

ok

CM> * make the new attributes take precedence over the old ones, in case 
CM> both are specified

Yes (see above link)


CM> And for the moment, until we decide what to do with our more general DOM
CM> improvements:

CM> * have the "href" IDL attributes reflect xlink:href or href or src as 
CM> appropriate (per the precedence rule above) as an SVGAnimatedLength

CM> * introduce an

CM>      attribute DOMString src;

CM> on the interfaces for <cursor>, <feImage>, <image> and <script> and have
CM> it just reflect the base value.




-- 
 Chris Lilley   Technical Director, Interaction Domain                 
 W3C Graphics Activity Lead, Fonts Activity Lead
 Co-Chair, W3C Hypertext CG
 Member, CSS, WebFonts, SVG Working Groups

Received on Tuesday, 21 August 2012 13:51:28 UTC