Personally, I find the discussion of "colour-modes" for maps misleading. Maps
have colours, selected by the developers of a map style based on their own
criteria and preferences. If you change those colours (you want them darker? a
different background? inverted? etc.) then you are creating a new map style — a
completely new one, or a variation of an existing one, it doesn't matter, they
are distinct.
As a new map style, its most appropriate place in the website settings is the
Map Layers selector, which is already implemented and working. No need of
anything else.
Openstreetmap-carto, with darkened tiles, for me, is a new style. It can be
implemented as such. It should never replace carto as the default on the
website.
Filters which act on top of a map style are going against the desired outcomes
that the makers of the style are seeking. I am personally against that idea.
If you want to introduce them anyway, then they should be controlled by
optional settings. There should be no "auto" feature. The default, regardless
of browser settings, should always be "No filter". And remember that most
people will use the website without a registered/logged-in user.
Honestly, I don't think many people desire a filter, so I wouldn't waste time
on it, but maybe it's just me.
Similarly, the UI is so minimal that a setting controlling light/dark would be
nice, but not crucial.
I feel we are wasting time on hypothetical thinking and niche user cases, while
ignoring the main desired feature: restoration of the default carto style, as
intended by its makers, for all users.
--
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/issues/5324#issuecomment-2521083604
You are receiving this because you are subscribed to this thread.
Message ID:
<openstreetmap/openstreetmap-website/issues/5324/2521083...@github.com>
_______________________________________________
rails-dev mailing list
rails-dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/rails-dev
