@schilpat The error isn't handled at all which suggests that this was a typo rather than deliberate way of handling the error... Since it's unhandled.

But please, do tell me more about how deselecting a normal setting in every modern web browser should break the entire website. It's an interesting way of coding I've not heard of before.

Sarcasm aside, there should at least be a message informing users of this, not a complete crash.

Hello, the problem is the following:

Uncaught Error: {"requestedAttributes":{"alpha":1,"stencil":1,"depth":1,"failIfMajorPerformanceCaveat":false,"preserveDrawingBuffer":false,"antialias":0},"statusMessage":"Could not create a WebGL context, VENDOR = 0xffff, DEVICE = 0xffff, GL_VENDOR = Disabled, GL_RENDERER = Disabled, Sandboxed = yes, Optimus = no, AMD switchable = no, Reset notification strategy = 0x0000, ErrorMessage = BindToCurrentSequence failed: .","type":"webglcontextcreationerror","message":"Failed to initialize WebGL"}
    at Jr._setupPainter (leaflet-gl.js:8:249460)
    at new Jr (leaflet-gl.js:8:238658)
    at new Vo (leaflet-gl.js:8:274848)
    at index.js:83:7451

Solution: Turn on Graphics Acceleration (a.k.a. Hardware Video Acceleration in Firefox.) And also the devs can fix that uncaught error so the page loads, lol.