- From: Amelia Bellamy-Royds via GitHub <sysbot+gh@w3.org>
- Date: Thu, 04 Jul 2019 17:11:28 +0000
- To: public-svg-issues@w3.org
AmeliaBR has just labeled an issue for https://github.com/w3c/svgwg as "Agenda+": == SVGAElement implements two conflicting interfaces == The [SVGAElement](https://svgwg.org/svg2-draft/linking.html#InterfaceSVGAElement) in the SVG 2 Linking chapter implements two interfaces where both two define their own `href` attribute: ```WebIDL SVGAElement implements SVGURIReference; SVGAElement implements HTMLHyperlinkElementUtils; ``` ```WebIDL [NoInterfaceObject] interface SVGURIReference { [SameObject] readonly attribute SVGAnimatedString href; }; ``` ```WebIDL [NoInterfaceObject] interface HTMLHyperlinkElementUtils { stringifier attribute USVString href; readonly attribute USVString origin; attribute USVString protocol; attribute USVString username; attribute USVString password; attribute USVString host; attribute USVString hostname; attribute USVString port; attribute USVString pathname; attribute USVString search; attribute USVString hash; }; ``` The spec does not say which definition should be followed, and I think this conflict shouldn't in the spec. Is this a problem can be fixed? See https://github.com/w3c/svgwg/issues/312
Received on Thursday, 4 July 2019 17:11:29 UTC