- From: Jesse McCarthy <notifications@github.com>
- Date: Tue, 10 May 2016 11:37:20 -0700
- To: whatwg/dom <dom@noreply.github.com>
- Cc:
- Message-ID: <whatwg/dom/issues/249@github.com>
I was wondering if it would be possible to provide greater visibility of `implements` relationships. Example: [interface `Element`](https://dom.spec.whatwg.org/#interface-element) implements [`ParentNode`](https://dom.spec.whatwg.org/#interface-parentnode), but it seems you can only find that out by looking at the definition of `ParentNode`. By greater visibility I mean displaying that relationship with the `Element` definition. That's what seems be done in the HTML spec, in one case at least: [interface `HTMLElement`](https://html.spec.whatwg.org/multipage/dom.html#htmlelement) lists several interfaces that it implements. With these 2 examples (`Element` and `HTMLElement`) the situation seems to be reversed. If it can only be one way, I (as a reader at least) would prefer the way it is for `HTMLElement` -- include the `implements` statements with the LHS interface. I'm guessing maybe it's organized the way it is for `Element` / `ParentNode` to aid maintainers in following the [advice](http://heycam.github.io/webidl/#idl-implements-statements) to not put a supplemental interface on the LHS of an `implements`? However, if there's a way to automate cross-referencing of these it seems like the best thing would be to show the relationship in both places (but only record it in one). I admit that I'm no expert on Web IDL, so hopefully that's not a nonsensical suggestion. What's the meaning of *mixin* in this spec -- an interface that's on the RHS of an `implements` somewhere? --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/whatwg/dom/issues/249
Received on Tuesday, 10 May 2016 18:37:48 UTC