New issue
Advanced search Search tips

Issue 918923 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Differentiate between main frame and subframe in Network::LoadingFailed

Reported by yasaswi....@gmail.com, Jan 3

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:64.0) Gecko/20100101 Firefox/64.0

Steps to reproduce the problem:
1. Attempt to load a page and it fail to load (Main frame request failed to load)

OR

1a. Load a page which contains an iFrame which fails to load (The subframe request failed to load).

What is the expected behavior?
Be able to easily distinguish whether it was the main frame or the subframe that failed to load. 

What went wrong?
The current recommended process involves: 

"Network.loadingFailed has a requestId, for which Network.requestWillBeSent reports frameId. You can use Page.getFrameTree to get all the frames with their ids, and also follow Page.frameXXX events if frames can change over time."

This seems fairly involved for information that is fairly easy to expose. 

Did this work before? N/A 

Chrome version: 73.0.3642.0  Channel: dev
OS Version: 
Flash Version: 

https://groups.google.com/a/chromium.org/forum/#!topic/headless-dev/5WK4UffcEW0
 
Whoops, meant to submit the issue from my @amazon.com email - vempatiy@amazon.com. 

I will be submitting a patch for this. Please let me know if this is something that you are willing to merge in. 
Labels: Needs-Triage-M73
Cc: dgozman@chromium.org susan.boorgula@chromium.org pfeldman@chromium.org
Labels: Triaged-ET
vempatiy@ Thanks for the issue.

As per comment #2, as a CL is provided, CC'ing dgozman@ and pfeldman@ from 'Platform>DevTools' component to look into this and help further.

Thanks..
Cc: -dgozman@chromium.org jarhar@chromium.org
Owner: dgozman@chromium.org
Status: Assigned (was: Unconfirmed)

Sign in to add a comment