Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ability to retrieve the original value of an overridden preference #38

Open
kizu opened this issue Sep 18, 2024 · 1 comment
Open

Ability to retrieve the original value of an overridden preference #38

kizu opened this issue Sep 18, 2024 · 1 comment

Comments

@kizu
Copy link

kizu commented Sep 18, 2024

(Copying from a mastodon thread with some rewording — https://front-end.social/@kizu/113160248251763608)

There are legit cases when you'd want to override the value that is used everywhere, but then still be able to differentiate how things look/behave based both on the original value, and on the override. See https://blog.kizu.dev/querying-the-color-scheme/#not-the-user-preference, for example — it is very similar to what we'll have with the web preferences.

With the way things are specified right now, we could do it in a hacky way: clear the override, read the value, restore the override, but that feels very cumbersome and inconvenient.

It would be great if we could get the original value natively (and also monitor it similar to matchMedia maybe).

@bramus
Copy link

bramus commented Nov 19, 2024

While I understand the use-case, this — unlike the override itself — would add an extra bit of tracking data.

By only having access to the overridden value, entropy is added to the tracking data. If we were to expose the original value, the opposite happens.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants