some javascript pages can't be accessed in the Sources tab but they show up in Network tab
Reported by
bennetth...@gmail.com,
Nov 23
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.102 Safari/537.36 Steps to reproduce the problem: 1. Go to https://www.voanews.com/ 2. Before or after the page loads, hit F12 to open debugger tools and open the Sources tab. 3. Observe that under www.voanews.com, there is only one URL listed beginning with "res?" -- this one: https://www.voanews.com/res?callback=_resourceLoaderReceiver_2&dependencies=navigation_horizontal,navigation_horizontal_sticked,program_updater (see pic1.jpg) 4. Switch to the Network tab and sort the url requests by the Name column. 5. Observe: there are three URLs listed beginning with "res?": https://www.voanews.com/res?callback=_resourceLoaderReceiver_0&dependencies=header,facebook_api,youtube_iframe,collapsible,highlights,hljson_loader,navigation_mobile,image_enhancer,smooth_scroll,google_translate,content_sharing,load_more,content_tabs,slider_nav_tabs,most_popular,simple_captcha,analyticstag_event,flexible_iframe,slider,back_to_top,whatsapp_share_button,multimedia_player_utils,multimedia_player_flash,multimedia_player_mpd,multimedia_player_analytics,multimedia_player_core,multimedia_player_ui,sticky_player_pangea_video,sticky_player_youtube,sticky_player_history_handler,sticky_player,copy_to_clipboard,lt https://www.voanews.com/res?callback=_resourceLoaderReceiver_1&dependencies=facebook_video_snippet,sticky_player_facebook https://www.voanews.com/res?callback=_resourceLoaderReceiver_2&dependencies=navigation_horizontal,navigation_horizontal_sticked,program_updater (see pic2.jpg) Since those URLs were requested successfully, they should also be accessible under the "Sources" tab, but they're not. 6. Also, if you right-click on the request for the third res? url, the context menu has the option "Open in Sources panel" (see pic3.jpg). But if you right-click on one of the other two requests, the "Open in Sources panel" option is missing. This is a problem for me because I'm trying to set a debugging breakpoint inside one of the first two js files, but it's not showing up under Sources. What is the expected behavior? All three of the "res?" javascript files should be listed under Sources. (Also, if you select those requests in the Network tab and view the Response sub-tab, it shows the contents, so they're not empty files.) What went wrong? Of the three "res?" javascript files, only one of them shows up in the Sources tab. It's possible that Chrome gets confused because all three files have the same URL up to the "?", and they only differ in the query string portion, so maybe Chrome thinks they are "the same URL". But they definitely have different content. Did this work before? N/A Chrome version: 70.0.3538.102 Channel: stable OS Version: 10.0 Flash Version: n/a
,
Nov 26
,
Nov 26
Bisected to https://chromium.googlesource.com/chromium/src/+log/ffab7376..07d8ae55?pretty=fuller Judging by the range a similar/same problem was wontfixed in bug 795023 . Maybe this time it'll get fixed?
,
Nov 26
This looks like a different problem. In 795023 they were talking about a file that shows up in the sources list, but when you try to open the file, it's empty. In this bug, the file in question doesn't show up in the sources list at all.
,
Nov 27
Able to reproduce the issue on reported chrome version #70.0.3538.102, latest stable #70.0.3538.110 and latest chrome #72.0.3622.0 using Windows 10, Ubuntu 17.10 and Mac OS 10.13.6 by following steps as per comment#0. Observed that out of the three "res?" javascript files in the network tab, only one of them displays in the Sources tab. The behaviour is seen from old M-60 builds(#60.0.3112.113). This is a non-regression issue hence marking it as untriaged and requesting someone from the dev team to look into the issue. Thanks.!
,
Nov 29
It looks like there is a sourceURL in those files. //# sourceURL=sticky_player.js This is causing them to appear as scripts under "(no domain)" as "sticky_player.js" and "sticky-player-facebook.js". I'm not 100% on how source URLs are supposed to behave in cases like this, but it appears to be working as intended.
,
Dec 4
Comment #6 explains what is wrong in this case. Sources and Network are largely orthogonal. There can be sources that are dynamically generated, there are network requests that do not produce any sources or scripts get collected in the virtual machine. There can be source urls and source maps. |
||||
►
Sign in to add a comment |
||||
Comment 1 by viswa.karala@chromium.org
, Nov 25