- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Wed, 27 May 2020 20:48:51 +0000
- To: public-css-archive@w3.org
It didn't morph (from that definition). That definition is "if the user preference doesn't match author preference, the author preference wins", which is exactly what the spec recently said (before I removed it this morning). That's also exactly what Safari does, if I'm understand you correctly. (Now it's the behavior of the spec in all cases, fwiw.) The difference is if the author and user preferences don't match, but the author *didn't* use the "only" keyword. Rune reverse-engineered the algo (8.2 in his proposal) to be "use the browser default in that case". Safari apparently actually does "auto-fix the author's colors to match the user preference". This issue is now about: what are those auto-fixes, and should we specify that in the spec? -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5089#issuecomment-634931195 using your GitHub account
Received on Wednesday, 27 May 2020 20:48:53 UTC