[svgwg] Should we move more HTMLElement members to HTMLorSVGElement mixin?

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

== Should we move more HTMLElement members to HTMLorSVGElement mixin? ==
@annevk made the good point when [making the change to include a HTMLorSVGElement mixin](https://github.com/whatwg/html/pull/3543#issuecomment-375579673) that there are other members on HTMLElement that would probably make sense to include in SVGElement via the mixin. click() is one example.

I'd like us to discuss on the call if we want to adopt any of these for SVG. For reference:
* [newly defined HTMLOrSVGElement mixin
](https://html.spec.whatwg.org/multipage/dom.html#htmlorsvgelement)
* [The other members currently on HTMLElement](https://html.spec.whatwg.org/multipage/dom.html#htmlelement)


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

Received on Friday, 23 March 2018 20:24:41 UTC