No styles are recognised in the Style pane
Reported by
cont...@jaygeorge.co.uk,
Dec 18 2016
|
|||
Issue descriptionDevTools failed to link network resource to filesystem. Platform: <Linux/Win/Mac> Chrome version: Version 57.0.2955.0 What are the details of your project? - URL format — http://somesite.local/blog/post.php?s=2015-11-27-some-page - Build System: grunt - HTTP server: apache Assets failed to link (or incorrectly linked): 1. Sites/somesite.com/perch/addons/feathers/default/css/style-dev.css If possible, please attach a screenshot of network sources navigator which should show which resources failed to map This is not the network sources, but my screenshot shows one issue, which is where no styles are recognised on a p tag (even though styles have clearly loaded on the screen)
,
Dec 19 2016
,
Dec 19 2016
A few questions: 1. Is this an issue with the Persistence2.0 experiment? 2. Are there any errors on devtools-on-devtools? 3. Can you reproduce this constantly? If you can, any chance you can share the webpage or come up with a jsbin demo page?
,
Dec 19 2016
> 1. Is this an issue with the Persistence2.0 experiment? Yes > 2. Are there any errors on devtools-on-devtools? I didn't check > 3. Can you reproduce this constantly? If you can, any chance you can share the webpage or come up with a jsbin demo page? I cannot at the moment. I updated Canary today. I'll update in the next few days depending or not if I can replicate
,
Dec 19 2016
Thanks! Next time it happens, could you please check for the errors on the devtols-on-devtools? They would help significantly
,
Dec 20 2016
OK it just happened again:
Here is the error with DevTools on DevTools, along with a screenshot of DevTools on DevTools (right window), and the regular DevTools not picking up styles (left window)
inspector.js:993 TypeError: Cannot read property 'sourceURL' of null TypeError: Cannot read property 'sourceURL' of null
at SDK.CSSStyleRule.SDK.CSSRule (inspector.js:3962)
at SDK.CSSStyleRule (inspector.js:3972)
at new SDK.CSSMatchedStyles (inspector.js:3654)
at SDK.CSSModel.callback (inspector.js:3842)
at callback (inspector.js:3301)
at InspectorBackendClass._AgentPrototype.dispatchResponse (inspector.js:3308)
at SDK.Target._onMessage (inspector.js:3265)
at SDK.MainConnection._dispatchMessage (inspector.js:3440)
at Common.Object.dispatchEventToListeners (inspector.js:395)
at innerDispatch (inspector.js:993)
,
Dec 20 2016
By the way, I can temporarily fix the problem by deleting the mapping, closing/reopening DevTools, re-adding the mapping. It comes back after a few page loads though. Not sure of exact steps to replicate, but it happens on multiple domains.
,
Jan 18 2017
Similar issue started happen to me a few weeks ago. Styles are displayed correctly for a while, but after couple of refreshes, they're gone until I close and open DevTools again (see screenshot - image at the bottom shows state when DevTools were reopened w/o page refresh)
,
Jan 18 2017
Yep, FYI this is still happening to me but can't figure out exactly what triggers it. No doubt if you spend an hour or two working on a site and writing CSS in Devtools you'll see it happen.
,
Jan 20 2017
For me it happens every ~15min. Always on page reload. Once it happens, I have to reload devtools as nothing else seems to be helping (changing panes, panels, inspecting other elements, reloading page). Error is triggered by "CSS.getMatchedStylesForNode" response (response object - https://gist.github.com/kdzwinel/a7e5a0f7dfd2d4548057be83fdd67001 ). SDK.CSSModel doesn't seem to know about a stylesheet that is referenced in that response (see image).
,
Jan 23 2017
|
|||
►
Sign in to add a comment |
|||
Comment 1 by ajha@chromium.org
, Dec 18 2016