- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Fri, 19 Jul 2024 17:29:53 +0000
- To: public-css-archive@w3.org
> so I probably need to migrate to match the spec
Don't worry about it.
> Add to the privacy section, at the very least an inline issue to signpost that it needs filling in.
Doesn't need much since there isn't *actually* a privacy concern, but it would be good to highlight *why* there isn't, yes, along the lines of what we've discussed in the issues. Maybe something like:
> The {{PreferenceManager}} object allows querying some user-preference [=media features=]. This is not a privacy leak, as that information was always trivially available by using the [=media features=] themselves in the normal fashion.
>
> The {{PreferenceManager}} object also allows overriding these user-preference [=media features=]; this is also neither a privacy nor accessibility regression, as the [=media features=] were already trivially ignorable by simply not querying them.
--
GitHub Notification of comment by tabatkins
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/pull/10597#issuecomment-2239727645 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 19 July 2024 17:29:54 UTC