Javascript files under Sources tab -> Sources subtab not showing after F5 until closing and reopening developer tools
Reported by
pere.pas...@gmail.com,
Mar 18 2016
|
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.87 Safari/537.36 Steps to reproduce the problem: 1. Update Chrome to 49.0.2623.87 m (previous version didn't have this issue) 2. Try to debug some javascript from some HTML page. Go to Sources tab; then in the Sources subtab try to find the source file for the javascript you want to debug, in order to put some breakpoints in there. If it hasn't passed too much time since you loaded your page and it's the 1st time, maybe you're luck and a kind of "tree" of sources will appear, starting from an icon depicting a window called "top". From there there are hanging, at least in my case, some children, all depicted with a cloud. In my case I search for the one titled "localhost" or "(no domain) (which contains the dynamically loaded ones). Open the file with double click and put a breakpoing on the desired place. 3. Do some javascript-involved action in your browser, hopefully the debugger will stop at your breakpoint. But if, for any reason, you've had to reload your page, for instance because you made some modifications in an external program or IDE, after that you'll find that, when trying to find your sources in the tree referenced in (2), there is no content. Only the folders added manually to your workspace will be there, which are of no use if they are, for exemple, .php or .aspx files which have to be interpreted by the webserver and developer tools won't allow you to put js breakpoints on them. Amazingly, if you close developer tools and reopen them, the tree is back again. What is the expected behavior? The source tree for the js files in use in the current html page should be displayed, as happened in (2) for the first time. It should be kept there no matter how many times you pressed F5, and What went wrong? Javascript source files tree in Sources tab -> Sources tooltap disappeared and won't appear again until you close and open Developer Tools. Did this work before? Yes Always; I just updated to this version and it's the 1st time I encounter this problem Chrome version: 49.0.2623.87 Channel: stable OS Version: 10.0 Flash Version: Shockwave Flash 21.0 r0 Yeah; you did it again, people. I switched from Firefox to Chrome due to their increasing list of critical, absurd bugs. Now this is happening again with Chrome. In the last months I get very afraid every time Chrome shows there's an update and that I have to reload in order to apply it. I tend to delay any updates as much as I can, because the number of regressions that affect my productivity increases exponentally with every new version, but sometimes I just cannot avoid it. I'm still missing the magnifying glass me that, for years, took me directly to the precise css style rule that was being applied in a certain page/element. I filed a bug for this, the empty space for placing the magnifying glass it's still there, but it simply isn't, and instead you have to look manually one after the other into the rules list being loaded in that page until you find the one that's being applied, which is very tedious. I still cannot find a reason why you removed this feature, and there's no answer/solution for those who, as me, complain.
,
Mar 21 2016
How can this be done?
,
Mar 21 2016
It would be really nice if you clarify if this is a joke or not - I'm already losing time trying to accomplish your request...
,
Mar 21 2016
re #c3: 1. Undock DevTools into separate window (from the three dots menu in the right). 2. Press Ctrl+Shift+I (Cmd+Opt+I) while focus is on DevTools window. 3. In newly opened window go to console and paste it's contents here. Thank you!
,
Mar 21 2016
Thanks a lot, dgozman. I promise I googled for it but got tired because "open devtools in devtools" didn't return any significant results...
Well, certainly there is an error. To be more specific, there's a warning and there an error:
(warning icon) FileError is deprecated. Please use the 'name' or 'message' attributes of DOMError rather than 'code'.
(error icon) inspector.js:1487 TypeError: Cannot read property '_deferredScrollIntoView' of null TypeError: Cannot read property '_deferredScrollIntoView' of null
at Object.TreeElement.reveal (inspector.js:1822)
at Object.WebInspector.NavigatorUISourceCodeTreeNode.reveal (chrome-devtools://devtools/bundled/sources_module.js:858)
at Object.WebInspector.NavigatorView.revealUISourceCode (chrome-devtools://devtools/bundled/sources_module.js:730)
at Object.WebInspector.SourcesNavigatorView.uiSourceCodeAdded (chrome-devtools://devtools/bundled/sources_module.js:995)
at Object.WebInspector.NavigatorView._addUISourceCode (chrome-devtools://devtools/bundled/sources_module.js:697)
at Object.WebInspector.NavigatorView._uiSourceCodeAdded (chrome-devtools://devtools/bundled/sources_module.js:699)
at Object.WebInspector.Object.dispatchEventToListeners (inspector.js:767)
at Object.WebInspector.ProjectStore.addUISourceCode (inspector.js:7339)
at Object.WebInspector.ContentProviderBasedProject.addUISourceCodeWithProvider (inspector.js:7937)
at Object.WebInspector.NetworkProject._addUISourceCodeWithProvider (inspector.js:8165)
,
Mar 22 2016
Thank you for providing more feedback. Assigning to requester "caseq@chromium.org" for another review. For more details visit https://sites.google.com/a/chromium.org/dev/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 22 2016
Ok, after further tests and not being able to reproduce it in private mode nor in Canary, it seems this behaviour is caused by some extensions. I observed that having any of those two extensions (a couple of different versiones of MeasureIt) active will cause the error to happen: pokhcahijjfkdccinalifdifljglhclm aonjhmdcgbgikgjapjckfkefpphjpgma
,
Mar 22 2016
,
Apr 28 2016
,
Jun 20 2016
Can't reproduce, even with pokhcahijjfkdccinalifdifljglhclm installed. Could you find aonjhmdcgbgikgjapjckfkefpphjpgma - it must have been deleted.
,
Jun 20 2016
I can still see it at Google Chrome Store: https://chrome.google.com/webstore/detail/measureit/aonjhmdcgbgikgjapjckfkefpphjpgma?utm_source=chrome-app-launcher-info-dialog
,
Sep 29 2016
,
Sep 29 2016
,
Feb 22 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/870b0bed803975d8ccd75a3af5ceff935214e2f5 commit 870b0bed803975d8ccd75a3af5ceff935214e2f5 Author: lushnikov <lushnikov@chromium.org> Date: Wed Feb 22 21:22:14 2017 DevTools: fix NavigatorView exception This patch fixes the "Cannot read property _deferredScrollIntoView of undefined" exception in navigator view. The navigator view assumes that there's only one project per frame; thus, when the project gets removed, it removes frame. However, in case of content script projects, there are multiple projects per frame, so the logic is incorrect. BUG= 596053 R=pfeldman Review-Url: https://codereview.chromium.org/2696143005 Cr-Commit-Position: refs/heads/master@{#452205} [add] https://crrev.com/870b0bed803975d8ccd75a3af5ceff935214e2f5/third_party/WebKit/LayoutTests/http/tests/inspector/sources/navigator-view-content-scripts-expected.txt [add] https://crrev.com/870b0bed803975d8ccd75a3af5ceff935214e2f5/third_party/WebKit/LayoutTests/http/tests/inspector/sources/navigator-view-content-scripts.html [modify] https://crrev.com/870b0bed803975d8ccd75a3af5ceff935214e2f5/third_party/WebKit/Source/devtools/front_end/sources/NavigatorView.js |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by caseq@chromium.org
, Mar 18 2016Components: -Platform>DevTools Platform>DevTools>Editing
Labels: Needs-Feedback