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

Issue 708507 link

Starred by 1 user
Status: Duplicate
Merged: issue 707733
Owner:
█ lushnikov@chromium.org
Last visit 29 days ago
Closed: Apr 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Developer Tools has CSS panel grayed out on refresh.

Reported by solilo...@gmail.com, Apr 5 2017 
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.98 Safari/537.36 OPR/44.0.2510.849 (Edition beta)

Steps to reproduce the problem:
1. Load a page, and open Dev Tools.
2. Inspect an element and note the CSS alongside.
3. Open it in responsive mode and refresh the page with dev tools open.
4. Now inspect the element and many a times, the panel is grayed out.

What is the expected behavior?
The panel would be still available for edit.

What went wrong?
The panel keeps turning gray. Upon closing Developer tools and opening the panel again, the problem goes away. Till it happens again.

Did this work before? N/A 

Chrome version: 57.0.2987.98  Channel: stable
OS Version: OS X 10.12.4
Flash Version:
Screen Shot 2017-04-05 at 8.52.26 AM.png
89.0 KB View Download

Comment 1 by solilo...@gmail.com, Apr 5 2017 

The CSS is not editable, and stays that way until I close Developer Tools and open it again. The Styles shown above are NOT being inserted dynamically. These are all contained in a file called main.css.

Comment 2 by allada@chromium.org, Apr 5 2017 

Can you please provide us with a test/demo of the issue?

Comment 3 by allada@chromium.org, Apr 6 2017

Labels: Needs-Feedback

Comment 4 by pfeldman@chromium.org, Apr 10 2017

Owner: lushnikov@chromium.org
Status: Assigned (was: Unconfirmed)

Comment 5 by lushnikov@chromium.org, Apr 13 2017 

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)

Comment 6 by lushnikov@chromium.org, Apr 13 2017

Mergedinto: 707733
Status: Duplicate (was: Assigned)
►

Sign in to add a comment