-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CSS advanced attr() function #513
Comments
N.B. these open css-values-4 issues: |
Hi @xiaochengh! @dbaron, @plinss, and I looked at this during the TAG F2F this week. We note that there is active discussion on the open issues I linked above, and we're happy to see that the CSS WG is trying to figure all of this out right now. Note that in the CSS WG, editors often add proposals to specs, which then get reviewed and resolved on by the WG. The TAG generally does our design review later in that process, after the WG resolutions. When these issues have been resolved, please come back to us and we'd be happy to review the result. |
Thanks! I'll wait until the CSSWG fixes the spec. |
Hi @hober! Could we please reopen this issue for TAG review or should I create a new one? We are planning to ship attr() in Chromium and currently there are no open CSSWG issues left for attr. Thank you. |
Hello TAG!
I'm requesting a TAG review of the advanced version of the CSS
attr()
function.The
attr()
CSS function is used to retrieve the value of an attribute of the selected element and use it in the stylesheet. There are two versions:content
property only as a string. This is already supported by all major browsers.You should also know that...
In CSS4, the feature has been substantially revised to ease implementations. Most importantly, it now works similar to
var()
, namely,attr()
is considered valid at parse time, and the actual validation of the attribute value is deferred to computed value time. Please review this version.We'd prefer the TAG provide feedback as (please delete all but the desired option):
💬 leave review feedback as a comment in this issue and @-notify
The text was updated successfully, but these errors were encountered: