-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Demo has issues #79
Comments
Yes, I noticed that. There are a couple of issues. First the client currently doesn't well respect the bounds that are set up by the The demo is also on a very old version of the client. Hopefully will get some time in the fall to bring everything up to date. I will close this issue when I get the CORB problem addressed. Thanks for commenting. |
Thanks @prushforth, my intention of using the demo today was to inspect image requests when navigating the map. There's alot happening in the world of images (and embeds) on the web concerning performance and user bandwidth, e.g: image Is this something you'd care to look at? Obviously this too applies to Leaflet, I may instead open an issue over there. However if (when?) Maps4HTML stop relying on Leaflet these are still things to consider. |
Leaflet is great, and its code has been how I learned what is good quality code, not that I reproduce that quality usually. As time goes by, I hope to move to first no dependencies and then to native code. But if such considerations apply to the |
There you go! :) Leaflet/issues/6283 |
No CORB issues anymore AFAICT, closing. |
In the demo at https://maps4html.github.io/Web-Map-Custom-Element/ alot of resources from https://geoappext.nrcan.gc.ca returns 404. It seems Cross-Origin Resource Blocking (CORB) is in effect.
The text was updated successfully, but these errors were encountered: