Issue metadata
Sign in to add a comment
|
Source display occasionally disappears.
Reported by
nige.ani...@gmail.com,
Oct 23
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.67 Safari/537.36 Steps to reproduce the problem: Like all these bugs I report, it's highly intermittent, and we have an app with *hundreds* of source files. So no, you are not getting a simple reproduction. Source just GOES and it's very irritating. Just like the debug tools stopping highlighting DOM nodes in the document when hovering them anywhere in the debugger, which you rejected because of no tiny repro example. It needs a complex app to bring the bug out. What is the expected behavior? What went wrong? See attachment. One source displays way down there, and the source I dblclick on does not appear at all. I have to restart my browser, and all 50 tabs. Did this work before? Yes 68 I think? Chrome version: 70.0.3538.67 Channel: stable OS Version: OS X 10.13.6 Flash Version:
,
Oct 24
Thanks for filing the issue! @Reporter: Could you please share a sample test file which helps us to triage this further in a better way. Any further inputs from your end may be helpful.
,
Oct 26
Sorry to hear that the source display is disappearing. Since we can't reproduce this yet, could you follow these instructions to open DevTools on DevTools: https://stackoverflow.com/a/12291163 and then send us a screenshot of the Console in the second DevTools in case there are any errors?
,
Oct 28
No. I can't just rustle up some simple HTML file with one script and say hey look! The source has gone! How could you imagine that is possible? People have *complex* applications these days. We have over a hundred modules imported. And it works *for hours at a time*. Then suddenly, unexpectedly, with no unusual activity, the sources go whappy.
,
Oct 28
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 29
Unable to reproduce the issue on reported chrome version #70.0.3538.67 using Mac OS 10.13.6 by following below steps. Steps: ===== 1.Launched chrome. 2.Navigated to "index.html" (attached the file for reference). 3.Navigated to Devtools->Sources tab. 4.Opened "common.js" file and observed that file got opened. Attached screencast for reference. As the issue is not getting reproduced at TE-end hence requesting someone from Dev team to look into the issue. Thanks.!
,
Oct 30
einbinder@, any ideas? I'm also unable to repro, and without seeing DevTools-on-DevTools errors, I'm not sure what we can do.
,
Nov 14
einbinder@ A gentle ping. Request you to check and respond to comment #7 and help in further triaging of this issue. Thanks..
,
Nov 14
Reporter, you've ignored the request in comment 3 to open DevTools on DevTools: https://stackoverflow.com/a/12291163 Please do that and copypaste the console output here.
,
Nov 16
Adding 'Needs-Feedback' label as per comment #9. nige.animal@ Request you to provide the console output following the steps provided in the above link, which will help in further triaging. Thanks..
,
Dec 5
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by phanindra.mandapaka@chromium.org
, Oct 23