Re: [svgwg] SVGAElement implements two conflicting interfaces

Another Possible solution:

Have `SVGURIReference` include `HTMLHyperlinkUtils`, so that it is clear which version has priority: the SVG definition overriding the inherited HTML definition. With the side effect that the hyperlink-decomposition properties (`origin`, `hash`, etc.) would be available on any SVG element with an `href` (or old `xlink:href`) attribute.



-- 
GitHub Notification of comment by AmeliaBR
Please view or discuss this issue at https://github.com/w3c/svgwg/issues/312#issuecomment-412636839 using your GitHub account

Received on Monday, 13 August 2018 19:33:06 UTC