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

Re DocumentAndElementEventHandlers, good catch! Edge does it per spec. Firefox does per spec but additionally adds to SVGElement via the mixin. Safari uses the mixin but includes it directly on Element. Chrome just adds directly to the Element interface (same net effect just not as clean IDL files).

I`m going to make a PR to add this mixin to SVGElement in Edge to match Firefox and what the spec probably should be. The other option would be to match Chrome/Safari and include the mixin on Element, but I`d personally prefer to match GlobalEventHandlers here. The net result in how devs will use the feature will be the same (unless some other mythical markup language comes along that inherits from Element and suppose to be interactive).

-- 
GitHub Notification of comment by dstorey
Please view or discuss this issue at https://github.com/w3c/svgwg/issues/395#issuecomment-375830570 using your GitHub account

Received on Saturday, 24 March 2018 00:19:45 UTC