- From: Xidorn Quan via GitHub <sysbot+gh@w3.org>
- Date: Fri, 03 Nov 2017 12:28:09 +0000
- To: public-css-archive@w3.org
> Firstly, there are a lot fewer places where `<string>` is accepted, and they are usually relatively less complicated than `<length>` and its friends when it comes to layout, so expanding them in used-value time (like what is currently done for content property) may not be as bad. It may not be as bad, but it could still be very bad. One issue comes to my mind is that `<family-name>` can be a `<string>`, and `font-family` is inherited, so you may really want to make `counter()` be expanded in computed-value time (rather than in used-value time like what we do now for `content`), otherwise it can lead to some funny behavior. This is some case which seems to be neither useful nor easy to implement, which would be a native consequence if we allow `counter()` be in anywhere `<string>` is allowed. I guess we should start this topic in a separate issue, now. -- GitHub Notification of comment by upsuper Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1026#issuecomment-341690025 using your GitHub account
Received on Friday, 3 November 2017 12:28:11 UTC