Fetch events are reported under Network, not XHR

Confirmed Issue #14047128 • Assigned to Jacob R.

Details

Author
Raymond C.
Created
Oct 2, 2017
Privacy
This issue is public.
Found in
  • Microsoft Edge
Reports
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

In DevTools/Network, Fetch calls are under the Other category, not XHR. I guess, technically, they aren’t the same as XHR, but I honestly thought Edge simply didn’t support reporting Fetch events. I’d put them under XHR (maybe rename to XHR/Fetch if not too big).

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Steven K.”

    • Hi Raymond,

      As you mentioned, XHR and Fetch are different APIs.  Fetch allows lower level network access and can “upgrade” to websockets (via a Fetch websocket creation API) as an example.  I will forward your request on as I am sure you are not the only one looking for Fetch requests in the XHR area.

      Thank you for the suggestion and feel free to add this feature request to the uservoice site.

      https://wpdev.uservoice.com/forums/257854-microsoft-edge-developer/category/87962-extensions?query=fetch

      The MS Edge Team

    • Wow, I had no idea about the upgrade to websockets. So to be clear, is this not the right place to file the issue/request and I should use the uservoice place instead?

    • This is the site for MS Edge browser issues with and emphasis on the Windows 10 Insider releases.  So your submission makes sense to me to be here.  Except, I think it is debatable about how to handle Fetch.  After looking at the details of the submission and seeing how Fetch doesn’t really fit in the XHR bucket, I think it should go to the uservoice page.

      I am also forwarding this on for internal comment, however, I believe this will end up as a “feature request” and this bug report will be closed as "By Design", I know not awesome word choice but I can see how this happens given Fetch isn’t XHR.

      I hope that makes sense.  Appreciate the submission, as I hadn’t thought about this in detail before now.  :-)

      Steve

    • Microsoft Edge Team

      Changed Assigned To to “edgedevtoolstri@microsoft.com”

      Changed Assigned To from “edgedevtoolstri@microsoft.com” to “Jacob R.”

      Changed Status to “Confirmed”

    You need to sign in to your Microsoft account to add a comment.

    Sign in