- From: Una Kravets via GitHub <sysbot+gh@w3.org>
- Date: Wed, 11 Nov 2020 14:58:05 +0000
- To: public-css-archive@w3.org
> I would much prefer a functional notation e.g. `current()`, with `current(color)` aliased to `currentColor` and `current(background-color)` resolving to what is proposed here. This would allow us to gradually extend it into other properties for which this kind of thing can be safely implemented, without introducing new keywords and new syntax that people have to learn. As a bonus, it would also allow us to add other arguments in the future, if we so decide. I love the extensibility behind this functional syntax for `current()`. My only concern here would be that this might significantly increase overhead for implementors. For example, `current(background)` could be valid in many cases instead of `current(background-color)`, yet not always (i.e. if there are images and multiple backgrounds). That leaves it to the author to require more value management and overhead. `currentBackgroundColor` limits the value options and is explicit to what you're getting. Would the property list be limited to a specific set of options, such as those that only accept single-value properties like `current(border-top-color)`? This also reminds me of `text-decoration-thickness: from-font;`, as it would be able to be written `text-decoration-thickness: current(font-weight)`. There are likely many usecases for this beyond color, so I do like this exploration, I'm just worried about complexity and management cost vs. benefit. -- GitHub Notification of comment by una Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5292#issuecomment-725470871 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 11 November 2020 14:58:11 UTC