Do we need to replace DOMStringMap?

[dirkschulze]

When updating links from HTML5.1 CR to HTML 5.2 I couldn't find an interface for DOMStringMap in the newer spec. Do we have to replace our use of it on the dataset attribute for SVGElement? Or did it move to a different page of the HTML5 spec and I just oversaw it?

[dstorey]

It is defined here: https://html.spec.whatwg.org/multipage/dom.html#domstringmap

I think this is ok as it is though as HTML has already moved out dataset into a shared mixin for HTML and SVG to use: https://html.spec.whatwg.org/multipage/dom.html#htmlorsvgelement

We just need to update to include that mixin. I'm unblocked on doing that now the new syntax has been merged.

[dirkschulze]

@dstorey So far we reference HTML5 exclusively I think. Would be the first WHATWG reference in the SVG spec.

[dstorey]

I believe we decided on the call to update to use WhatWG for now as there are things in WHATWG that we need that are not in W3C HTML. And if that became a problem at CR then we could look into it again. There are already some references to WhatWG (Fetch, links in linking.html for #AElementRelAttribute et al.)

[AmeliaBR]

For what it's worth, W3C HTML has DOMStringMap defined: ED, 5.2

But yes, we've already decided to switch to WHATWG so we can use the HTMLOrSVGElement mixin to harmonize these types of things, so that will take care of that.