We have moved to mapbox-gl-js for quite some time now (over 2 years) and indeed one of the side effects is that older browsers with no WebGL support are not displaying the maps.
hm… that’s strange, we haven’t done any change recently that should affect that part of the site. Unfortunately I don’t have an apple device to check. Maybe there will be an error in browser console but I don’t think it is easy to get it in iphone and ipad, maybe if this is reproduced on a mac we can find out.
Please also add details about the browser (which one) and its version. Thanks!
I tried enabling webgl 2 in Settings - Safari - Experimental features and restarted Safari, but hat did not make the map appear. A reboot of the ipad did not make the map appear either.
I can install Safari on my PC later today to check if there are any messages in the console.
Does the Satnogs web site have some sort of change tracking? I searched amon the librespace repos on gitlab, but wasn’t able to find anything that looked like it could contain the web site.
The map on db isn’t displaying on Chrome. ( Version 83.0.4103.116 (Official Build) (64-bit) On Windows 10) The maps on network do display properly for me on Chrome right now.
From the Firefox console: Content Security Policy: The page's settings blocked the loading of a resource at blob:https://db.satnogs.org/ebba93da-d366-4172-a1e8-500c0b2bec43 ("script-src").
Under Chrome 83.0.4103.106 (OSX) I can’t load the map either:
mapbox-gl.js:33 Refused to create a worker from 'blob:https://db.satnogs.org/3eba46fa-0f96-4b0e-a0c0-8aeb28bf8cdc' because it violates the following Content Security Policy directive: "script-src 'self' https://*.google-analytics.com 'unsafe-eval' https://db-satnogs.freetls.fastly.net". Note that 'worker-src' was not explicitly set, so 'script-src' is used as a fallback.
Please re-do your tests/checks using your available browsers against network-dev.satnogs.org and db-dev.satnogs.org and confirm that you can see the map fine. If everything works, soon we will deploy the changes in production, after finishing some other ongoing work.
Was this ever fixed for production version? I’ve previously had this issue on Firefox, so I switched to Safari. Since this thread has started I’ve also had issues on all other browsers and devices. Any tips? I thought that it’s because of restrictive web browser or some adblock, but it happens on devices without any blocking as well. Thanks!