Web-Map-Custom-Element
Web-Map-Custom-Element copied to clipboard
A custom <mapml-viewer> and <layer-> element suite
Discovered in #887 Steps to reproduce: 1. visit the [sandbox](https://maps4html.org/web-map-doc/demo/sandbox/) and paste in the following code ```html ``` 2. Expected behavior - we think the layers should not be fetched...
Currently a layer can be created that contains only a `` template, meaning it doesn't draw anything, but it will return features or info from a server on interaction. It...
Refactor leaflet specific events into map- namespace. ### mapml-viewer/web-map **Changed:** * locationfound -> map-locationfound * locationerror -> map-locationerror * ~~preclick -> map-preclick~~ * movestart -> map-movestart * move -> map-move...
As pointed by @yhy0217 When removing a map-extent from a single layer in a map, the other map-extents should be used to calculate the projection of the layer. Relevant to...
Using the technique used by @yhy0217 in #905, we should go over our testing specifically for web-map and mapml-viewer who have duplicate files testing the same thing and merge them...
This issue is to collect use cases and references from PRs and other issues. The origin of this is #675, but also the need to re-build our proposal as [a...
Some things seem to have fallen through the cracks, should have localized strings available for them: - [ ] zoom in/out buttons - [x] default "Layer" label / accessible name...
refactor custom events dispatched by mapml-viewer so they don't clash with leaflet events, ex. "zoomend" -> "map-zoomend". All events - https://maps4html.org/web-map-doc/docs/api/mapml-viewer-api#events https://github.com/Maps4HTML/Web-Map-Custom-Element/blob/94fa0896a87504777bb58c808e0b5f805926b2cf/src/mapml-viewer.js#L619-L852
Corresponding [documentation](https://github.com/Maps4HTML/web-map-doc/issues/130), [spec](https://github.com/Maps4HTML/MapML/issues/253), [extension](https://github.com/Maps4HTML/mapml-extension/issues/64), and [experiments](https://github.com/Maps4HTML/experiments/issues/121) issues
A lot of our tests currently rely on web servers to fetch data. Upon our conversation with @yhy0217 & @prushforth we decided it would be good to not be reliant...