- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 19 Jun 2019 16:27:26 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `Disallow repetition of color-scheme keywords?`, and agreed to the following: * `RESOLVED: computed value of color-scheme match its specified value` <details><summary>The full IRC log of that discussion</summary> <dael> Topic: Disallow repetition of color-scheme keywords?<br> <dael> github: https://github.com/w3c/csswg-drafts/issues/3848<br> <futhark> I was trying but Tab can present<br> <dael> TabAtkins: for future extensibility we allowed arbitrary keywords and they're ignored. Question is what happens when you repeat color-scheme keyword? We don't want to disallow, but do we keep it in computed value? Collapse along the way?<br> <dael> TabAtkins: No strong argument either way<br> <dael> TabAtkins: originally thoguth there was an efficiency argument but that's not true if trying to preserve unknown. I think conclusion is keep the same and don't simplify.<br> <dael> TabAtkins: Just have computed value = specified value<br> <futhark> I’m fine with either, it’s just that dropping duplicates means having to keep track of them during parsing<br> <dael> astearns: Any comments?<br> <futhark> Which requires a hash map or something<br> <dael> astearns: So close no change?<br> <dael> TabAtkins: I don't recall current state<br> <dael> TabAtkins: Let me look<br> <dael> TabAtkins: It would be changing spec<br> <fantasai> Proposal is to resolve no change [in the value] :)<br> <dael> astearns: That computed is same as specified value<br> <dael> TabAtkins: Yes<br> <dael> astearns: Obj to computed value of color-scheme match its specified value?<br> <dael> RESOLVED: computed value of color-scheme match its specified value<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3848#issuecomment-503633417 using your GitHub account
Received on Wednesday, 19 June 2019 16:27:28 UTC