[css-backgrounds] <color> in <shadow> should default to currentcolor #2766
Labels
Closed Accepted by CSSWG Resolution Commenter Satisfied
Commenter has indicated satisfaction with the resolution / edits.
css-backgrounds-3
Current Work
fx-filter-effects-1
Comments
When we get agreement on this, it would be a change to color 4 and an erratum on color 3. |
Let's put it into agenda... but next telecon is not apac timezone one which can be hard for me to take part in so maybe sydney f2f... |
This also affects
It should use currentcolor as well, I suppose. |
I agree that referencing |
The Working Group just discussed
The full IRC log of that discussion<myles> Topic: <color> in <shadow> should default to currentColor<myles> Github: https://github.com//issues/2766 <myles> Fantasai: any objections? <chris> rrsagent, here <RRSAgent> See https://www.w3.org/2018/07/03-css-irc#T23-20-25 <myles> Rossen: We need to make sure the people who care have a chance to look <myles> xidorn: the issue is that if it isn’t specify, the used color is taken from the current property <myles> xidorn: I think the text should just be “it defaults to currentColor” <myles> dbaron: the spec may have evolved from something that was more flexible <myles> chris: let’s say it’s user defined <myles> Rossen: are we okay with the proposed resolution? <myles> Rossen: any objections? <silence> resolved <chris> s/let/(sarcastically) let/ <myles> RESOLVED: Accept the proposal <Rossen> s/Accept the proposal/<color> in <shadow> should default to currentcolor <myles> chris: There’s also the same problem with drop-shadow as well as shadow <myles> leaverou: it doesn’t work that way already? <myles> Rossen: any additional comments? <myles> Rossen: <silence> Any objections? <myles> RESOLVED: drop-shadow and shadow will also default to currentColor |
fantasai added a commit that referenced this issue
Aug 3, 2018
…not some unnamed thing with the same behavior). #2766
fantasai added the Commenter Satisfied Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Currently the spec says:
It seems to behave like
currentcolornowadays, but it would have different behavior in terms of interpolating. I think we should probably make it default tocurrentcolorinstead. I see no reason we need a separate no-color value case.(It's not clear to me whether it should go to level 3 or 4.)
The text was updated successfully, but these errors were encountered: