Move dataset & other shared IDL attributes from SVGElement to HTMLOrSVGElement about svgwg

[domenic]

We would appreciate it if in working collaboratively with us, you did not then turn around and request that another group copy our work so that you can proceed to ignore our work in your spec :(.

[AmeliaBR]

I don't think dataset can be generalized to all XML languages (because of the expectations it creates re valid attributes), so putting it on Element is unlikely to happen.

However, it may be preferable to define it within the DOM specs as a "mixin" interface that can then be implemented by both HTMLElement and SVGElement. That would ensure that we had one, canonical definition that would always be updated consistently.

Anyone want to take responsibility for looking into this possibility with HTML WG and WHATWG?

[dstorey]

There is now a PR for this and blur/focus/tabindex in HTML whatwg/html#3543

[dstorey]

To be clear, we're moving this to a mixin in HTML (tests pending) that will still be included on SVGElement, rather than moving it to Element.

[annevk]

In the above referenced commit I said that it fixed this issue, but I guess what still remains is that you need to remove dataset from SVGElement's IDL.

[AmeliaBR]

Yep, marking this as "needs edits" and updating the title to match the chosen solution.

[AmeliaBR]

This brings up again the issue of whether SVG wants to link normatively to WHATWG interfaces; we currently reference W3C versions. With the new WHATWG royalty commitments, it's probably less of an issue, but still a little messy & political to make the change.

I'll file an issue on W3C/html to ask if they can mirror the change, but not sure how long that might take.

[css-meeting-bot]

The Working Group just discussed (Revisiting) Move dataset & other shared IDL attributes from SVGElement to HTMLOrSVGElement.

The full IRC log of that discussion

<BogdanBrinza> topic: (Revisiting) Move dataset & other shared IDL attributes from SVGElement to HTMLOrSVGElement
<BogdanBrinza> GitHub: https://github.com//issues/60
<BogdanBrinza> dstorey: SVG 2.0 current draft already links to the Fetch specification so we won't make things worse in PR if we add another one
<BogdanBrinza> Resolution: Link to WHATWG spec now to resolve github.com//issues/60, while Liam is confirming this with W3C