CSS3 attr() function for all properties
Categories
(Core :: CSS Parsing and Computation, enhancement)
Tracking
()
People
(Reporter: amir123456789893, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:85.0) Gecko/20100101 Firefox/85.0
Steps to reproduce:
Hi, I have faced a problem it can be solved with JS but the CSS attr() function will be a lifesaver now the web needs this kind of feature.
As I know, now in 2021 attr() function is just available for CSS content property, it can be practical if we can have attr() function for all properties just a simple example like this.
Actual results:
What should happen:
Expected results:
What really happens (now):
|
Reporter | |
Updated•5 years ago
|
|
|
Reporter | |
Comment 1•5 years ago
|
||
What happens: https://s16.picofile.com/file/8425934692/false.png
What should happen: https://s16.picofile.com/file/8425934692/false.png
|
|
Reporter | |
Comment 2•5 years ago
|
||
(In reply to amir123456789893 from comment #1)
What happens: https://s16.picofile.com/file/8425934692/false.png
What should happen: https://s16.picofile.com/file/8425934692/false.png
What should happen: https://s17.picofile.com/file/8425935276/true.png
|
||
Comment 3•5 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::JavaScript Engine' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.
|
||
Updated•5 years ago
|
|
||
Comment 4•5 years ago
|
||
This is handled by bug 435426, right?
|
|
Reporter | |
Comment 5•5 years ago
|
||
(In reply to Mats Palmgren (: mats) from comment #4)
This is handled by bug 435426, right?
Nobody does talk about it last reply is for 7 months ago and this is not good after years, is it in progress? how can I see the process?
|
||
Comment 6•5 years ago
|
||
This is in fact just bug 435426. As far as I can tell, experimentation is not particularly blocked by anything (I'd happily mentor that bug), though actually shipping the feature is probably blocked on reaching consensus on issues like https://github.com/w3c/csswg-drafts/issues/5092 and https://github.com/w3c/csswg-drafts/issues/5136.
Description
•