Peter Rushforth

I interpret this in terms of [speculative polyfills](https://www.w3.org/2001/tag/doc/polyfills/#don-t-squat-on-proposed-names-in-speculative-polyfills) for a (proposed, nearly standard) but as yet unknown element. > If we embrace this restriction, instead of fighting it, we have...

@domenic > I'm not sure I understand that suggestion, or the connection to speculative polyfills. I can understand your confusion, I should have been clearer. I think the term speculative...

> LAPIs are not able to use magic (like defining custom elements with non-dashed names) OK I get it, nothing new, they build on what is already there.

> I would go so far as arguing that the lack of this capability in WFS was one important reason that prevented its uptake compared to WMS. If WFS had...

It's been a couple of years and I was wondering if there has been any progress on this issue. I see that it's called "simplification" in the charter.

I saw that someone over there [said ](https://github.com/whatwg/html/issues/389#issuecomment-246830104) that `` should respond to CSS `transform: scale(...)`, however I tested and could not reproduce that. The [spec](https://html.spec.whatwg.org/multipage/image-maps.html#the-area-element) has a note that...

> Or were you just looking into it for perhaps demonstrational purposes? I was hoping to provide a non-scripted responsive fallback for areas in my [GeoServer plugin](https://github.com/Maps4HTML/geoserver/tree/master/src/community/mapml), which serves the...

> Using CSS, the only thing I can think of is to override the coords attribute to absolutely position elements with percentage offsets i.e. left: 10%; top: 20% (which should...

@Malvoz looks interesting, and most importantly, functional. I don't understand it all yet, but from what I see, we would need to generate a top/left % scale for each area...

@malvoz, I did notice, and thanks you were right I needed them :-)