Re: [csswg-drafts] [css-backgrounds] <color> in <shadow> should default to currentcolor

The Working Group just discussed `<color> in <shadow> should default to currentColor`, and agreed to the following:

* `RESOLVED: Accept the proposal`
* `RESOLVED: drop-shadow and shadow will also default to currentColor`

<details><summary>The full IRC log of that discussion</summary>
&lt;myles> Topic: &lt;color> in &lt;shadow> should default to currentColor<br>
&lt;myles> Github:<br>
&lt;myles> Fantasai: any objections?<br>
&lt;chris> rrsagent, here<br>
&lt;RRSAgent> See<br>
&lt;myles> Rossen: We need to make sure the people who care have a chance to look<br>
&lt;myles> xidorn: the issue is that if it isn’t specify, the used color is taken from the current property<br>
&lt;myles> xidorn: I think the text should just be “it defaults to currentColor”<br>
&lt;myles> dbaron: the spec may have evolved from something that was more flexible<br>
&lt;myles> chris: let’s say it’s user defined<br>
&lt;myles> Rossen: are we okay with the proposed resolution?<br>
&lt;myles> Rossen: any objections? &lt;silence> resolved<br>
&lt;chris> s/let/(sarcastically) let/<br>
&lt;myles> RESOLVED: Accept the proposal<br>
&lt;Rossen> s/Accept the proposal/&lt;color> in &lt;shadow> should default to currentcolor<br>
&lt;myles> chris: There’s also the same problem with drop-shadow as well as shadow<br>
&lt;myles> leaverou: it doesn’t work that way already?<br>
&lt;myles> Rossen: any additional comments?<br>
&lt;myles> Rossen: &lt;silence> Any objections?<br>
&lt;myles> RESOLVED: drop-shadow and shadow will also default to currentColor<br>

GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at using your GitHub account

Received on Tuesday, 3 July 2018 23:24:25 UTC