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

Issue 695147 link

Starred by 1 user
Status: Duplicate
Merged: issue 681492
Owner:
█ lushnikov@chromium.org
Last visit 29 days ago
Closed: Mar 2017
Cc:
█ lushnikov@chromium.org
█ brajkumar@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Styles tab stops displaying elements, must refresh page to show elements again

Reported by derek...@gmail.com, Feb 22 2017 
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.54 Safari/537.36

Steps to reproduce the problem:
1. Inspect element
2. Select an element
3. Alter some CSS

What is the expected behavior?

What went wrong?
Developer Tools just displays nothing in the styles tab when inspecting elements after making a change thus making me refresh the page after every element change.

Did this work before? Yes 

Chrome version: 57.0.2987.54  Channel: beta
OS Version: 10.0
Flash Version: Shockwave Flash 24.0 r0

I honestly don't know of any other way to explain the problem other than the panel just doesn't show anything at all like in the screenshot. I've even reinstalled Chrome and cleared my Developer Tools AppData.
C5RqyPKVYAA6ODl.jpg
118 KB View Download

Comment 1 by woxxom@gmail.com, Feb 22 2017 

Invoke devtools-for-devtools by pressing Ctrl-Shift-I inside a floating (undocked) devtools window and check if there are any errors in the console.

Comment 2 by nyerramilli@chromium.org, Feb 23 2017

Labels: Needs-Bisect Needs-Triage-M57

Comment 3 by derek...@gmail.com, Feb 23 2017 

Hmm, looks like it does have some errors.


Main._createAppUI: 31.5ms
inspector.js:8510 Main._showAppUI: 30.0ms
inspector.js:8511 Main._initializeTarget: 11.7ms
inspector.js:919 TypeError: Cannot read property 'sourceURL' of null TypeError: Cannot read property 'sourceURL' of null
    at SDK.CSSStyleRule.SDK.CSSRule (inspector.js:3776)
    at SDK.CSSStyleRule (inspector.js:3786)
    at new SDK.CSSMatchedStyles (inspector.js:3468)
    at SDK.CSSModel.callback (inspector.js:3656)
    at callback (inspector.js:3117)
    at Protocol.InspectorBackend._AgentPrototype.dispatchResponse (inspector.js:3124)
    at SDK.Target._onMessage (inspector.js:3081)
    at SDK.MainConnection._dispatchMessage (inspector.js:3257)
    at Common.Object.dispatchEventToListeners (inspector.js:395)
    at innerDispatch (inspector.js:919)

Comment 4 by brajkumar@chromium.org, Feb 23 2017

Cc: lushnikov@chromium.org brajkumar@chromium.org
Labels: Needs-Feedback
derekbtw@ Could you please confirm is this issue is similar to  bug 681492  ?

Thanks!

Comment 5 by derek...@gmail.com, Feb 23 2017 

Yes, that's very similar. Sorry, I didn't see that thread before I posted.

Comment 6 by lushnikov@chromium.org, Feb 24 2017

Labels: -Pri-2 Pri-1
Owner: lushnikov@chromium.org
Status: Assigned (was: Unconfirmed)
Derek, any chance you can provide us with a URL of the website where you experience the issue? Also, could you please check Chrome Canary to see if this happens for you there as well?

Comment 7 by lushnikov@chromium.org, Mar 3 2017

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

Sign in to add a comment