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

The Working Group just discussed `Should we move more HTMLElement members to HTMLorSVGElement mixin?`.

<details><summary>The full IRC log of that discussion</summary>
&lt;BogdanBrinza> topic: Should we move more HTMLElement members to HTMLorSVGElement mixin?<br>
&lt;BogdanBrinza> GitHub: https://github.com/w3c/svgwg/issues/395<br>
&lt;BogdanBrinza> dstorey: Basic proposal - there are number of methods in HTML that might make sense to add to SVG<br>
&lt;BogdanBrinza> dstorey: click is one example, AmeliaBR added GlobalEventHandlers as potential one to add<br>
&lt;BogdanBrinza> dstorey: that all browsers but Edge support - so could be easy to add<br>
&lt;BogdanBrinza> AmeliaBR: regardless of the syntax would be useful to add to SVG anyway somehow<br>
&lt;BogdanBrinza> liam: Might be a good one to consider when we have tests<br>
&lt;BogdanBrinza> BogdanBrinza: given that 2+ browsers support this today - seems like capturing the truth, not a functional change<br>
&lt;BogdanBrinza> AmeliaBR: for additional features might want to be careful and make sure we have tests that verify no new major features are added as part of the effort<br>
&lt;BogdanBrinza> liam: Given that might affect ability to ship SVG 2.0 would like to defer to future<br>
&lt;liam> [Liam opposed to adding support for "lang" without i18n review]<br>
&lt;AmeliaBR> Proposed Resolution: Add DocumentAndElementEventHandlers mixin to SVGElment or HTMLOrSVGElement mixin if and only if at least two implementations pass tests; defer discussion of rest of the issue<br>
&lt;BogdanBrinza> Resolution: Add DocumentAndElementEventHandlers mixin to SVGElment or HTMLOrSVGElement mixin if and only if at least two implementations pass tests; defer discussion of rest of the issue<br>
&lt;BogdanBrinza> action: DStorey to add tests as discussed on the meeting just now<br>
&lt;trackbot> Created ACTION-3867 - Add tests as discussed on the meeting just now [on David Storey - due 2018-04-02].<br>
&lt;liam> [i can go and ask but pretty sure the answer is no, we should link to w3c html not to whatwg w3c. one reason is we need to link to a specirfic dated version in normative docs]<br>
</details>


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

Received on Monday, 26 March 2018 19:02:47 UTC