Yes:
For Firefox, the equivalent is: open about:config and set webgl.forbid-software to false, then restart Firefox. If the map still doesn’t load, start Firefox from a terminal with LIBGL_ALWAYS_SOFTWARE=1 firefox — this forces Mesa’s software renderer (llvmpipe), which supports everything the map needs. Please avoid webgl.force-enabled — that would use the old Intel driver directly and is likely what caused the crashes you saw. Software rendering will be noticeably slower than the old map, unfortunately — that’s inherent to running the GPU work on the CPU.
Yes, we updated our map library, which now render maps in your browser, instead of downloading prerendered images. This technique is commonplace in most mapping software nowadays and where actually kind of late to adopt this.
Maybe I misunderstood your reply. so you see the spinning cube even without the special startup parameters for chrome? Then there might be something else on our end. But we do require webgl for the use of Kurviger now and will require webgl2 in a few months. Both technologies are widely available and supported almost all devices nowadays.