New issue
Advanced search Search tips

Issue 670456 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner:
Closed: Nov 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 3
Type: Bug



Sign in to add a comment

CSS Coverage doesn't work on pages with dynamically generated styles

Project Member Reported by rkj@google.com, Dec 1 2016

Issue description

Chrome Version       : 57.0.2937.0
OS Version: OS X 10.12.1
URLs (if applicable) :
Other browsers tested:
  Add OK or FAIL after other browsers where you have tested this issue:
     Safari 5:
  Firefox 4.x:
     IE 7/8/9:

What steps will reproduce the problem?
1. Go to angular application (like go/awn-nightly)
2. Record the css coverage in timeline
3. Notice there is no way to see the results.

What is the expected result?

The results would be accessible.

What happens instead of that?

As Angular is not generating css files to include in the app, but instead inserts <style> tags dynamically in the document there is no way to inspect the results. The sources for the html file do not have inserted styles, and the "Elements" tab doesn't have this annotation.

Please provide any additional information below. Attach a screenshot if
possible.

UserAgentString: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2937.0 Safari/537.36



 

Comment 1 by ajha@chromium.org, Dec 2 2016

Components: Blink>CSS
Labels: M-57

Comment 2 by ajha@chromium.org, Dec 2 2016

Cc: ajha@chromium.org
Components: -Blink>CSS Platform>DevTools
Owner: caseq@chromium.org
Status: Assigned (was: Unconfirmed)
Looks like Timeline has changed to Performance but somehow I am not seeing css coverage there.

caseq@: Could you please take a look at this and help in further investigation.

Thank you!

Comment 3 by caseq@chromium.org, Nov 28 2017

Status: WontFix (was: Assigned)
It actually works, as long as generated stylesheets provide /*# sourceURL=... */ comment, check out devtools-on-devtools for an example. We filter others out on purpose, as we won't be able to provide a meaningful identification for these in UI. I don't think coverage information has much value unless it can be traced to the original source file.

I think angular now shouldn't at least strip sourceURL comments if they're there, isn't this the case?

Sign in to add a comment