New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 707733 link

Starred by 4 users

Issue metadata

Status: WontFix
Owner:
Last visit 29 days ago
Closed: Dec 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

DevTools says styles are in style tags, not in link tags

Reported by sindre.0...@gmail.com, Apr 3 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36

Steps to reproduce the problem:
1. Style a web app with SCSS, add source maps (or go to http://orkide.preprod.acos.no)
2. Inspect an element
3. Hard reload the page

What is the expected behavior?

What went wrong?
The resource field should say e.g `_default.scss`, not `<style></style>`, as styles are external and no style tags are present.

Did this work before? Yes 

Chrome version: 57.0.2987.133  Channel: stable
OS Version: 10.0
Flash Version: Shockwave Flash 25.0 r0
 
chrome-bug.PNG
285 KB View Download
Labels: Needs-Triage-M57
Cc: rbasuvula@chromium.org
Labels: Needs-Feedback
Tested in chrome # 57.0.2987.133 and Canary #59.0.3062.0 on win 10.0 & 7 and Please find the screen shots for your reference.
Steps followed:
1. Navigate to provided url in chrome and open devtools.
2. Inspect an element and reload the page.>> Getting default.scss..

@Reporter: Could you please let me know if i have missed anything and if possible,Please create new profile without extensions and apps.Re-check once let us know the observations and expected behavior of the issue which would help us to triage the issue further.

Thanks in Advance.
707733.PNG
1.4 MB View Download
Maybe try another hard reload? This is not very scientific, I'm afraid, but I've had it happen with multiple PCs (all running Win10), multiple accounts, with and without extensions running, and in Chrome 57 (personal PC and browserstack), 58.0.3029.41 beta (64-bit) and 59.0.3061.3 canary (64-bit). I'm not able to reproduce this error in Chrome 56.0.2924.87 (Browserstack, Win10).

Steps that seem to produce this error with a 100% rate: 
Long hard reload (keeping ctrl+f5 down for a bit).
Project Member

Comment 4 by sheriffbot@chromium.org, Apr 4 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "rbasuvula@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: -Needs-Triage-M57
Owner: lushnikov@chromium.org
Status: Assigned (was: Unconfirmed)
Thanks you for the bug report, we are able to reproduce it and will look further into it.
Cc: lushnikov@chromium.org
 Issue 708507  has been merged into this issue.
For the record: it looks like the InspectorNetworkAgent::FetchResourceContent fails to fetch css content. Might be because of resource_data_ running out of allocated space (which is currently defined in  g_maximum_total_buffer_size and which is 100Mb)

This would explain the "flaky" nature of the bug, because resources get discarded on a fifo-basis.
Labels: -Pri-2 Pri-1
Labels: -Pri-1 Pri-2
Can we have another repro URL for this?

The http://orkide.preprod.acos.no/ no longer works
Cc: mmanchala@chromium.org
 Issue 725619  has been merged into this issue.
Status: WontFix (was: Assigned)
I failed to repro this. Speculatively closing this unless there's a good repro.

Sign in to add a comment