New issue
Advanced search Search tips

Issue 734470 link

Starred by 7 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

CSS Coverage with @imported stylesheets

Reported by christop...@wetteronline.de, Jun 19 2017

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.86 Safari/537.36

Steps to reproduce the problem:
1. Create a website using a CSS stylesheet that uses @import to import another CSS stylesheet
2. Press "Start recording and reload page" in the "coverage" panel for that site
3. Stop the recording after the reload

What is the expected behavior?
The CSS coverage of both stylesheets should be recorded

What went wrong?
Instead only the CSS coverage of the first CSS stylesheet is shown. The @imported stylesheet isn't considered for coverage.

Did this work before? No 

Chrome version: 59.0.3071.86  Channel: n/a
OS Version: 
Flash Version:
 
Labels: Needs-Triage-M59
Cc: pbomm...@chromium.org
Labels: pre-stable-59.0.3071.86 M-59
 christoph.petzold@ if possible can you please provide test page for faster triage of the bug.
Labels: Needs-Feedback
Owner: caseq@chromium.org
Status: Assigned (was: Unconfirmed)
Here is a test page.

There are two stylesheet files, style1.css and style2.css. Both affect the site and style one element each. But CSS coverage only considers style1.css
index.html
139 bytes View Download
style1.css
76 bytes View Download
style2.css
50 bytes View Download
We are seeing the same issue with code coverage and @import in Chrome 65.0.3325.181.

It does not appear to be isolated to Linux. We see it on Mac and Windows too.

This bug appears to be marked “needs-feedback.” Does it need feedback/an additional test case for triaging?

If so, we might be able to help.

Comment 7 by ruvi...@gmail.com, Apr 26 2018

Have same problem on Windows. There is many missing files, including @import-ed
Bumped into this today on Chrome 70. Do you need any additional information to help boost this along its way?
Known issue. No immediate plans to fix. 
I think everyone here knows they shouldn't use @import in production.
Ideally coverage would work with it in development, but I don't know we'll resolve this anytime soon

Sign in to add a comment