You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
@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.
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.
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: