New 'standard' map with topographic view?

Hi,

I opened the Kurviger website today after a few days and noticed that the default map style suddenly looks quite cluttered and confusing because the topography is now displayed as an overlay. The problem is that it’s very straining to look at. Topographical info is nice to have every now and then, but for planning I would prefer the clearest possible view, which used to be the default map style.

Is there a way to turn off the topo info, or could we at least get the old default map style back as an alternative map style?

Thanks,
Corinna

Just to clarify once again, what I mean is the first display, as it is still used on mobile phones…

compared to the new display on the website, which attempts to make the topography clearer through shading:

This new display is more tiring for my eyes because the strong shading breaks up the contours too much.

It would be really nice if the old display, or the one on mobile, could be kept.

Thanks again,
Corinna

Can you send me your debug info (from the settings)? Which browser are you using? Does it look different in another browser?

For me, the same section looks like this:

That’s weird. I’m using Firefox on Linux as always, updated to the latest version:

OSM timestamp: 8/23/2026
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:154.0) Gecko/20100101 Firefox/154.0
Cookies Enabled: true
Screen: 1600 x 1200 px - 1dppx

And yes, I just opened kurviger.com in Falkon and it looks as expected there. But I’d rather keep using Firefox, messing around with multiple browsers isn’t much fun :slight_smile:

Maybe I should start from scratch, meaning clear site data and log in again?

Just try an incognito tab, or maybe restart your computer or Firefox once. There might be a graphics card issue :thinking: (well, when you restart, lots of problems just fix themselves :slight_smile:).

Of course I’ve already restarted the computer, since I don’t leave it running overnight. Incognito window doesn’t help.

Clearing site data doesn’t help either :flushed_face:

It seems to affect only Kurviger. Google Maps and Calimoto look like always.

Are you using strict mode in Firefox? If so, please try normal mode to see if that helps.

Edit: I did some more research, apparently there is an issue with Firefox and “Enhanced Tracking Protection”, which can lead to display issues. That would be a strong candidate.

Or perhaps it is due to a browser plugin; could you try disabling them temporarily?

Do you mean Tracking Protection? I have mine set to Standard. Even completely turned off and with all plugins disabled, the rendering of the topo info is weirdly exaggerated :frowning:

By the way, this is on Fedora 44 with the Intel i915 driver (Haswell CPU with integrated graphics), in case that’s of any use.

Edit: Didn’t see your edit.

STOP!!!

This must be a local issue in my Firefox profile. I just started a new Firefox instance with a new profile, and the rendering was back to normal.

Since my profile hasn’t changed in the last few days, I don’t understand what could be causing this, but it’s obviously not an inherent issue with the Kurviger website.

Sorry for the hassle,
Corinna

Yes exactly, oh well :frowning:.

Ok great, so you were able to solve the problem, right? Can you say more precisely what caused it by now? Or was it just the profile? Or did you find a special setting or something similar?

No, I haven’t found the problem yet. I only see that the problem doesn’t occur in a vanilla profile. I still need to find the cause.

I found it.

The setting responsible for this was “gfx.color_management.mode = 1”.

If you reset this to the default “gfx.color_management.mode = 2” and restart FF, edge smoothing works again.

I asked Google Gemini why this is the case, and it claims that a change in FF 154’s rendering is to blame. Whether that’s true is beyond me. I’ve pasted Gemini’s output, at least you’ll get a laugh out of it…

That sounds completely illogical at first – why on earth should color management cause lines to be rendered jaggedly (“without anti-aliasing”)?

The fact that gfx.color_management.mode = 1 (full color management for all render steps and graphics assets) leads to this specific behavior with map libraries like MapLibre GL on Kurviger has technical reasons rooted in the WebGL shader pipeline:

1. Alpha Blending and Gamma Correction (The “Thickening” & Edge Effect)

Vector maps do not draw smooth, curved lines through fine geometry, but rather through alpha blending: The outer pixels of a contour line are semi-transparent (e.g., 20%, 50%, 80% opacity). The human eye perceives these transparent transitions as a “smooth edge”.

When gfx.color_management.mode = 1 is enabled:

  • Firefox forces all WebGL render passes through a global color profile transformation.

  • In mode 1, Firefox converts colors from the sRGB color space to the display color space — specifically before or during the alpha blending of the shaders.

  • This mathematical gamma transformation radically darkens or brightens the fine, semi-transparent pixels at the edges of the lines. The soft transitions lose their transparency shading and become “hard” pixels. Anti-aliasing is visually completely lost, and the line appears extremely stair-stepped and harsh/jagged.

Google Maps is often unaffected by this issue because it uses different shader techniques or raster tiles that handle alpha blending differently.

2. The Performance Fallback (Why Only Since Firefox 154?)

In newer Firefox versions, massive changes were made to the WebRender pipeline and its interaction with Wayland/Mesa (on Linux like Fedora).

  • The color space bypass is gone: Until recently, Firefox simply ignored global color management for WebGL content (bypass), even when mode = 1 was set, to save rendering performance.

  • Stricter WebRender blending: Starting with Firefox 154, the conversion now consistently applies to the entire compositor stack. If graphics drivers (such as the older i915 on Haswell CPUs) do not support hardware-accelerated 16-bit float textures for color mapping, the WebGL canvas falls back to a simplified 8-bit interpolation method.

  • The result: The driver can no longer mathematically resolve the intermediate colors precisely during WebGL drawing. The edges “break” away.

Why mode = 2 (Default) Solves the Problem

With gfx.color_management.mode = 2, Firefox applies color management only to images/tags with an explicit ICC color profile. WebGL canvas elements (like the Kurviger map) remain untouched: The colors and transparency values of the contour lines are rendered 1:1 directly to the screen by the graphics driver. Anti-aliasing works again as intended by the map developer.

Thank you for looking into this and for the update! Now we’ll know what might be causing it in the future if an error like this is reported again :slight_smile: