L2 optimization drops some new css styles
See original GitHub issueLike the subject line says…
Note that content-visibility
is a new style included in latest versions of browsers.
Input CSS
.listitem { display: flex; scroll-snap-align: start; scroll-margin-top: 0; content-visibility: auto; }
Actual output CSS
incorrect with 2: { all: true }
.listitem{scroll-snap-align:start}
Expected output CSS
correct with 2: { all: false }
.listitem{display:flex;scroll-snap-align:start;scroll-margin-top:0;content-visibility:auto}
Issue Analytics
- State:
- Created 3 years ago
- Comments:7
Top Results From Across the Web
Sass Style Guide | CSS-Tricks
Use Your Regular CSS Formatting Rules / Style Guide This includes things like: Be consistant with indentation. Be consistant about where spaces ...
Read more >How to write a CSS hack for IE 11? [duplicate] - Stack Overflow
So I found my own solution to this problem in the end. After searching through Microsoft documentation I managed to find a new...
Read more >neps/nep-0014-dropping-python2.7-proposal.html at main
<title>NEP 14 — Plan for dropping Python 2.7 support — ... <link href="_static/styles/theme.css?digest=92025949c220c2e29695" rel="stylesheet">.
Read more >Cascading Style Sheets (CSS) Working Group Teleconference
smfr: I'd like to build up the understanding of how they should work incrementally. I have some data from real sites that will...
Read more >Front-End Performance Checklist 2021 (PDF, Apple Pages ...
Have we optimized enough with tree-shaking, scope hoisting, code-splitting, ... And if you need something custom, you can use ...
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 FreeTop 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
Top GitHub Comments
Cool, I’m glad it works fine now. Please reopen if needed, and sorry it took me a while to have a look at it.
@jakubpawlowicz i’m running clean-css 4.2.3
i’ve tested again and yes, the rule is correct but split into two separate rules. for some reason, it all works now - i know it didn’t use to work with older chrome when i opened this issue 4 months ago.
thanks.