By making the setting available to other apps I meant iD of course. Its color 
scheme preferably should match the entire site, that means it has to know 
somehow whether to use `prefers-color-scheme` or ignore it. Let's suppose we 
made this setting somehow readable through the api. iD will look at it and 
adjust its color scheme accordingly.

Now let's suppose we don't use iD embedded in the osm-website. We'll run it 
from https://ideditor-release.netlify.app/, It can still read the setting in 
the api, but the reason to apply it is gone because iD is no longer embedded. 
Then maybe it's better to pass it as a startup parameter through
https://github.com/openstreetmap/openstreetmap-website/blob/22942b1ca144444bdece1636451fd3ad86530b3e/app/views/site/_id.html.erb#L4
In this case we wouldn't need to worry how exactly we store the setting.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/pull/5337#issuecomment-2480721621
You are receiving this because you are subscribed to this thread.

Message ID: 
<openstreetmap/openstreetmap-website/pull/5337/c2480721...@github.com>
_______________________________________________
rails-dev mailing list
rails-dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/rails-dev

Reply via email to