[svgwg] SVGAElement implements two conflicting interfaces

• From: Kagami Sascha Rosylight via GitHub <sysbot+gh@w3.org>
• Date: Wed, 05 Apr 2017 06:05:39 +0000
• To: public-svg-issues@w3.org
• Message-ID: <issues.opened-219477697-1491372338-sysbot+gh@w3.org>

SaschaNaz has just created a new issue for https://github.com/w3c/svgwg:

== 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?

Please view or discuss this issue at https://github.com/w3c/svgwg/issues/312 using your GitHub account

Received on Wednesday, 5 April 2017 06:05:46 UTC