sourceURL and document.write do not play together nicely.
Reported by
b...@mavenomics.com,
Jan 4 2018
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.84 Safari/537.36 Steps to reproduce the problem: Here is a minimal reproduction https://jsfiddle.net/k4pLnv3j/1/ 1. click the button to open a new window. 2. open inspector in the new window. 3. click the button again. 4. set a breakpoint to the first line var a = 5. 5. resume debugging. 5. click the button again. 6. set a breakpoint to console.log line. there are now two myScript.js, one has a yellow tint. What is the expected behavior? there shouldn't be duplicated scripts in the debugger window. What went wrong? chrome can't distungish dynamically loaded script once it is updated. Did this work before? No Chrome version: 63.0.3239.84 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: same behavior exists with iframes and sourceURL.
,
Jan 5 2018
Able to reproduce the issue on reported version 63.0.3239.84 and latest canary 65.0.3311.3 and beta 64.0.3282.71 using Mac 10.12.6, Ubuntu 14.04 and Windows-10 hence providing Bisect Info Bisect Info: ================ Good build: 63.0.3237.7 Bad build: 63.0.3238.0 You are probably looking for a change made after 507896 (known good), but no later than 507897 (first known bad). https://chromium.googlesource.com/chromium/src/+log/0bf476948928a005903a89c541f460f3b115c988..f323d18e8e9c1ef839bdc050a6a94a36b7ce9101 Reviewed-on: https://chromium-review.googlesource.com/710376 @Alexey Kozyatinskiy: Please confirm the issue and help in re-assigning if it is not related to your change. Adding ReleaseBlock-Stable as it seems recent break, feel free to remove it if not applicable. Thanks!
,
Jan 5 2018
CC'ing: lushnikov@chromium.org, as the author(kozyatinskiy@chromium.org) last visit is 23 days ago
,
Jan 11 2018
,
Jan 19 2018
This issue is marked as a release blocker with no milestone associated. Please add an appropriate milestone. All release blocking issues should have milestones associated to it, so that the issue can tracked and the fixes can be pushed promptly. Thanks for your time! To disable nags, add the Disable-Nags label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Feb 12 2018
This issue is marked as a release blocker with no milestone associated. Please add an appropriate milestone. All release blocking issues should have milestones associated to it, so that the issue can tracked and the fixes can be pushed promptly. Thanks for your time! To disable nags, add the Disable-Nags label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 26
viswatejarayalu.karala@: Could you please check if this is still an issue on the latest stable?
,
Jul 27
Able to reproduce the issue on latest chrome stable# 68.0.3440.75 and latest chrome# 70.0.3503.0 using Mac 10.12.6, Windows-10 and Ubuntu 16.04, hence adding appropriate labels to it. Thanks!
,
Oct 4
I checked this one in latest Google Chrome Canary and in current Google Chrome Stable and beta - it works. Feel free to open another issue if you still can reproduce it. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by krajshree@chromium.org
, Jan 4 2018