CSSUsage not finding all stylesheet content
See original GitHub issueSplit out from https://github.com/GoogleChrome/lighthouse/issues/6628#issuecomment-485275120
Provide the steps to reproduce
What is the current behavior?
LH reports that the fonts don’t have font-display properties. The CSSUsage artifact does not contain the content of any of the stylesheets.
What is the expected behavior?
LH does not report the fonts are missing font-display
, and the CSSUsage artifact contains the content of the stylesheets.
Environment Information
- Affected Channels: CLI
- Lighthouse version: v4.3.0, v5.0.0
Issue Analytics
- State:
- Created 4 years ago
- Reactions:6
- Comments:13
Top Results From Across the Web
Complete list of reasons why a css file might not be working
Are you sure the stylesheet is loaded ? You can see it using the "Net" tab of Firebug on firefox, or on "Network"...
Read more >Organizing your CSS - Learn web development | MDN
A good tip is to add a block of comments between logical sections in your stylesheet too, to help locate different sections quickly...
Read more >How to Link CSS to HTML Files in Web Development - Hostinger
In this detailed guide, you'll learn how to link a CSS style sheet to HTML and the many reasons why you would want...
Read more >CSS style sheet not loading or linking with HTML
I'm using HTML with Bootstrap all loads up fine, but when a style sheet is added to the HTML code sometimes it doesnt...
Read more >Style Sheets in HTML documents - W3C
The examples included below all use the CSS (Cascading Style Sheets) language [CSS1], but other style ... Not all style sheet languages support...
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
I’ll assign myself to the interim fix that will quiet the false positive, but the true fix requires Chromium-support and there is no timeline for a fix there.
any update this issue ? styled-components ssr suffer this problem