Re: [svgwg] SVGAElement implements two conflicting interfaces

The SVG one should take precedence; it needs to, for backwards compatibility with SVG 1.1. 

But the IDL as written is definitely not clear about that.  I'm not sure if there's an easy way in IDL to represent that sort of polymorphic inheritance.  In other cases of a conflict (between an SVG 1.1 property and an interface with a same-named property), it's clear that the currently defined class member overrides the interface. But this is two different interfaces.

Either way, it's one more case of SVGAnimatedString being the bane of any attempts to harmonize SVG-DOM and HTML-DOM.





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

Received on Saturday, 8 April 2017 18:26:29 UTC