- From: jonjohnjohnson via GitHub <sysbot+gh@w3.org>
- Date: Wed, 14 Mar 2018 19:25:55 +0000
- To: public-css-archive@w3.org
After reading @AmeliaBR thoughts on `!add` I'm just gonna throw this out there...
Would a special keyword for the accessing the current cascades value, similar to `currentColor`, be simpler, as well as more flexible, allowing for authors to run their own operations within a `calc()` function? Possibly better than the unique notations of `!add` or`!multiply`?
So instead of this `!add` notation...
```css
.selector {
filter: grayscale(50%) !add;
}
```
How about `currentValue` allowing for these...
```css
.selector {
filter: grayscale(calc(currentValue) + 50%);
filter: grayscale(calc(currentValue) - 25%);
filter: grayscale(calc(currentValue) / 2);
}
```
Then people can just run whatever operations the value/type that was already in the cascade? Would currentValue need some sort of fallback if it was previously set to a different type? Like `currentValue(0%)` having a fallback of `0%` ?
--
GitHub Notification of comment by jonjohnjohnson
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1594#issuecomment-373145521 using your GitHub account
Received on Wednesday, 14 March 2018 19:25:58 UTC