Contact emails
Explainer
https://developer.mozilla.org/en-US/docs/Web/CSS/attr#Examples
Design docs/spec
Specification: https://drafts.csswg.org/css-values-4/#attr-notation
TAG review
https://github.com/w3ctag/design-reviews/issues/513
Summary
Implement the augmentation to attr() specified in CSS Level 4, namely, allowing various types (besides <string>) and usage in all CSS properties (besides pseudo-element 'content').
Note: CSS Level 4 has made substantial revisions to attr() compared to Level 3 to ease the implementation. We'll follow CSS4.
Motivation
This is a highly requested feature, with 77 stars at crbug.com/246571. We also want to keep it considered in the CR period by adding the first implementation.
Risks
Interoperability and Compatibility
No browser has implemented this feature yet. Even though there's no negative signals from other browsers, there's still a minimal interoperability risk that we end up the only implementation.
Firefox: No public signals (https://bugzilla.mozilla.org/show_bug.cgi?id=435426)
Edge: No public signals
Safari: No public signals (https://bugs.webkit.org/show_bug.cgi?id=26609)
Web developers: No signals
Will this feature be supported on all six Blink platforms (Windows, Mac, Linux,
Chrome OS, Android, and Android WebView)?
Yes
Is this feature fully tested by web-platform-tests?
No
There's some WPT coverage as for May 2020:
https://wpt.fyi/results/css/css-values?label=master&label=experimental&aligned&q=attr
We will introduce more tests: https://bugs.chromium.org/p/chromium/issues/detail?id=1081995
Tracking bug
https://bugs.chromium.org/p/chromium/issues/detail?id=246571
Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/4680129030651904
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAFqEGhbR2mhM5DYUj52qCB957y%2BbpZDb67qqumrd2w9JTAGHFw%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/050b47c3-5ee8-4f63-abea-28bdc2e0e9e7%40chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAKFBnUoogOgmLVmiKJ-BwWQ5hCxxcD_E74bO2Pem%2BxFpkCNXHA%40mail.gmail.com.
How will implementing this feature affect the parsing of div::before { content: attr(text) 1px; }?This sees like invalid syntax regardless of this feature (and I never saw personally)...Also, what is the original intention of div::before { content: attr(text) 1px; }?
I still do not get it... Is it because before this feature, attr(...) would be replaced at parse time?(I see that it is re-computed if you change the content of the attribute, which seems to contradict that it is being replaced at parse time)
Regarding the security concerns, it appears to me that this doesn't introduce extra security risks?We don't need attr() to exfiltrate sensitive data of a document. The attribute selector already allows that (I learned it from this article).So should it be a blocking issue if this feature doesn't introduce new vulnerabilities?
☆PhistucK
☆PhistucK
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscribe@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/050b47c3-5ee8-4f63-abea-28bdc2e0e9e7%40chromium.org.
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscribe@chromium.org.
☆PhistucK
☆PhistucK
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/050b47c3-5ee8-4f63-abea-28bdc2e0e9e7%40chromium.org.
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAKFBnUoogOgmLVmiKJ-BwWQ5hCxxcD_E74bO2Pem%2BxFpkCNXHA%40mail.gmail.com.