Closed AmeliaBR closed 4 years ago
I've just come across this myself, setting up some map layers I've created for the layer-related examples on another repository. I'll fix the Bing URLs and check everything else, and also see about setting up my localhost with HTTPS so I catch any future problems earlier.
Additionally, we could include
<!-- Should ideally come after <meta charset="utf-8">, but before all resources -->
<meta http-equiv="Content-Security-Policy" content="upgrade-insecure-requests">
in all the examples documents, to prevent future broken resources due to http:// links.
FYI I opened https://github.com/w3c/respec/issues/2485 earlier.
Thanks @NickFitz & @Malvoz for both fixes.
@NickFitz, can you go through your Bing API examples & make sure they're all using HTTPS URLs?
The HTTP URLs are being blocked as mixed content in my browser.
I'm also getting a number of other console errors on the page; I'm not sure if they're related to that script not being loaded, the stack traces are all MapBox scripts. Does Bing wrap around MapBox, or is that a bug in a separate demo?