Fetch Api - GET response type of 'json' is hidden when using XHR quick filter
Reported by
st...@originaleye.co.uk,
Dec 1 2016
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.98 Safari/537.36 Steps to reproduce the problem: 1. Do a 'GET' request using the fetch api. 2. View network tab. 3. Click on XHR quick filter. 4. OPTIONS request is visible. 4. GET request is not visible. What is the expected behavior? I would expect both the OPTIONS request and the GET request to be visible when filtering using the XHR quick filter in the network tab. What went wrong? The GET request is hidden when filtering on XHR only. Did this work before? N/A Chrome version: 54.0.2840.98 Channel: stable OS Version: OS X 10.11.6 Flash Version: Shockwave Flash 23.0 r0 This may be the designed behaviour but it's not consistent. Filtering using XHR is a common way of seeing AJAX requests. Showing the OPTIONS but not the GET is confusing and inconsistent.
,
Dec 2 2016
This issue seems to be TE out of scope. Hence, adding the label TE-NeedsTriageHelp. Thanks...!!
,
Dec 14 2016
I have no idea why the GET request is given the "json" type. NetworkDataGridNode.displayType() returns the MIME type only when the resource type is Other or Image. For the Fetch API, it should be Fetch. The XHR filter grabs resource types assigned to the Common.resourceCategories.XHR category, which are XHR, Fetch and EventSource. Seems for some reason, InspectorPageAgent::OtherResource is picked for the actual request of fetch() while XHRResource is picked for the preflight.
,
Dec 15 2016
,
Dec 13 2017
,
Oct 12
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by ligim...@chromium.org
, Dec 1 2016