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

Issue 649047 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Sep 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

DevTools does not show sources for some files.

Project Member Reported by flackr@chromium.org, Sep 21 2016

Issue description

Version: 53.0.2785.129 (Official Build) beta (64-bit)
OS: ChromeOS

What steps will reproduce the problem?
(1) Visit https://play.google.com/store/movies/collection/topselling_paid
(2) Open DevTools and try to view play.google.com > store/movies/collection > topselling_paid in the Sources tab.

What is the expected output?
Expect to see the source for this file.

What do you see instead?
Instead, I just see an empty pane with the following error message at the top of it:
XMLHttpRequest cannot load https://accounts.google.com/ServiceLogin?passive=...&osid=1&continue=https://notifications.google.com/u/0/coc&followup=https://notifications.google.com/u/0/coc&authuser=0. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'null' is therefore not allowed access.

I think the Sources pane is trying to separately fetch the resource and failing due to not having the correct origin to access it.

Please use labels and text to provide additional information.

 
Screenshot 2016-09-21 at 2.17.17 PM.png
157 KB View Download
Owner: kozyatinskiy@chromium.org
Status: Assigned (was: Untriaged)
Status: WontFix (was: Assigned)
In ToT it doesn't show an XMLHttpRequest error and shows correct source when page is reloaded with DevTools.
In case when DevTools is opened after page reload, resource for this script has already removed from caches and DevTools couldn't restore its content, so please reload your page with DevTools.



 Issue 675702  has been merged into this issue.

Comment 4 by phistuck@gmail.com, Dec 20 2016

My issue was merged into this issue, but I experienced this even after a reload.

Sign in to add a comment