You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The <properties> element can be used to create popups. It seems to be a case of browser magic, which may not be ideal.
Are authors expected to style the <properties> element itself (or even pseudo-elements) to style popups?
I think it'd be good to consider integration with the new Popover API instead. MapML could specify that HTML should extend the list of allowed popovertarget elements to include <feature>.
The text was updated successfully, but these errors were encountered:
I think it'd be good to consider integration with the new Popover API instead. MapML could specify that HTML should extend the list of allowed popovertarget elements to include .
+1
Also, I like the idea of <feature> being the one that contains the popover attribute / being the popovertarget i.e. not the <properties> alone, because it might allow the map author to supply CSS that is used when the feature is in the popped-over state to highlight the geometry on the map in some way, while the popover is displayed.
I'll read the MDN docs and see if we can add it to our polyfill roadmap.
The
<properties>
element can be used to create popups. It seems to be a case of browser magic, which may not be ideal.Are authors expected to style the
<properties>
element itself (or even pseudo-elements) to style popups?I think it'd be good to consider integration with the new Popover API instead. MapML could specify that HTML should extend the list of allowed
popovertarget
elements to include<feature>
.The text was updated successfully, but these errors were encountered: