Closed prushforth closed 1 year ago
Should we be moving our elements up here when they are working as custom elements?
One day, as we iterate closer to an HTML Standard PR, we should just treat all the elements as HTML elements, regardless of whether they're new (from MapML) or existing (updates to the spec). That section (3) is due to merging an earlier separate spec that we developed that separated the content we would expect in an HTML document type from the content that we might expect in a MapML document type. The line has blurred a bit with the concept of local and remote content, but I don't think custom / not really implemented is a good way to spec them out.
Should #247 be tackled here also? If you think that will interfere with the GeoServer work.
It wouldn't interfere, but it's related to <map-feature>
fwiw. We will get to it eventually.
Looks good to me! Seems to have everything from the map-extent PR! @prushforth Should https://github.com/Maps4HTML/MapML/issues/247 be tackled here also? If you think that will interfere with the GeoServer work.