Update stylesheet runtime to order psuedo state atomic declarations based on lvfha
See original GitHub issueAtomic declarations means user land ordering of pseudo states no longer is possible. We are going to bake in the order based on LVFHA:
Top to bottom, bottom takes precedence:
:link:visited:focus:hover:active
This ticket will modify the stylesheet runtime (used only when styles are baked in - once extracted this runtime is removed) to ensure the ordering.
One idea I have for this is to build the class name with knowledge of the pseudo state so we don’t have to do much at runtime.
Guiding principles:
- less is more
- code short as possible
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Webpack CSS extraction discussion · Issue #575 - GitHub
I really like the idea of compiled as you move as much css processing to the build step and shrink the runtime code...
Read more >Atomic CSS - Compiled CSS in JS
Atomic CSS is a method of reducing the total amount of defined rules by creating a single rule for every declaration — enabling...
Read more >HTML and CSS Tutorial - Nanyang Technological University
Basic HTML and CSS Tutorial for the beginners. ... An HTML document begins with a Document-Type Declaration <!DOCTYPE html> (Line 1) to identify...
Read more >Which of the following attributes values can be used to define a list ...
This is the reason that I combine both the HTML and CSS in this article as they are ... An HTML document begins...
Read more >HTML and CSS Tutorial: The Basics (2022) - Allass
Start with an initial CSS layout. Does website design start with CSS, NOT HTML? Work on your CSS: Divide your site into logical...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

There’s also
:focus-within, that should probably come before:focusThis is a concern for sure. But I personally wouldn’t go rebuild lots of things to avoid it