- From: Karl Dubost via GitHub <noreply@w3.org>
- Date: Wed, 29 Jul 2026 07:39:31 +0000
- To: public-svg-issues@w3.org
karlcow 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
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 29 July 2026 07:39:32 UTC