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

Issue 661198 link

Starred by 1 user
Status: WontFix
Owner:
█ lushnikov@chromium.org
Last visit 29 days ago
Closed: Nov 2016
Cc:
█ hdodda@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Javascript files although loaded but cannot be seen in source window of developer tool

Reported by haris...@gmail.com, Nov 1 2016 
UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.71 Safari/537.36

Steps to reproduce the problem:
1. Open a we page (calls a bunch of .js files)
2. Open chrome's dev tool source window
3. search for .js files that are loaded, they are not present there.

What is the expected behavior?
Source window should show all .js files called while loading a particular web page.

What went wrong?
I am using dojo heavily on the front end. Is there any configuration that I need to do in my project in order to reflect all .js files loaded for a web page. I can see them in Network's tab but in order to debug those files I need them in source window.

Did this work before? N/A 

Chrome version: 54.0.2840.71  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 23.0 r0

Comment 1 by hdodda@chromium.org, Nov 2 2016

Cc: hdodda@chromium.org
Labels: Needs-Feedback
Unable to reproduce the issue on Windows 7 using chrome stable M54 #54.0.2840.87 .

Attached screenshot for reference. All the js files loaded in browser are seen in source window of developer tool.

@haris -- Could you please try system restart and try with fresh chrome profile . If you still face the issue , please write us with your observations and provide us the .js files you loaded in browser.

Thanks!
661198.PNG
57.4 KB View Download

Comment 2 by woxxom@gmail.com, Nov 2 2016 

I'm seeing it occasionally (rarely) on various sites, also on extension background pages. So far I didn't notice what triggers the issue.

Comment 3 by haris...@gmail.com, Nov 2 2016 

I have fixed issue in my project. Apparently, chrome has moved its sourceURL parsing from DevTools to V8 and now, the regex for sourceURL doesn't match for the newer versions with what dojo has embedded into their framework. 
It will match //# or //@, but not the four slash variant (doubly commented directive). Look for ////@ sourceURL in one of your dojo js file and change it to //# sourceURL. It worked for me and now I can see all dojo js files loaded by the server for that particular page. Thanks.

Comment 4 by eostroukhov@chromium.org, Nov 2 2016

Owner: dgozman@chromium.org
Status: Assigned (was: Unconfirmed)

Comment 5 by dgozman@chromium.org, Nov 2 2016

Owner: lushnikov@chromium.org

Comment 6 by lushnikov@chromium.org, Nov 2 2016

Status: WontFix (was: Assigned)
Looks like the issue was mitigated.
►

Sign in to add a comment