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

Yeah, GlobalEventHandlers just uses the old syntax which should be fixed with Dirk's PR.

In general in Edge most things on HTMLElement are fairly trivial to implement on SVGElement as our implementation shares the same base class, unless the behavior is expected to differ in SVG. I'd have to look at what we do for Boolean content attributes like hidden to see if they would work correctly when ported over. hidden just basically sets the equivalent of display: none;

If Edge supports the content attribute for contenteditable"correctly"  in SVG then it is really trivial for me to add the IDL attribute . IF it is just that it sets it to contentEditable then that is a general reflect/attribute DOM bug in Edge that will get fixed anyway with work we're doing for an upcoming version.

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

Received on Friday, 23 March 2018 23:55:01 UTC