Closed Bug 1209382 Opened 6 years ago Closed 6 years ago
fetch requests don't show up as XHR requests
164.35 KB, image/png
30.51 KB, image/png
3.15 KB, patch
|Details | Diff | Splinter Review|
Note: This web app uses the native fetch API  which perhaps does things differently from jQuery.ajax or ng-http or one of those. The web app has a polyfill  but I don't think it's kicking into effect in Fx 43. Perhaps the XHR badge is based on the `X-Requested-With: XMLHttpRequest` header. Either way, it's XHR and so it should have the badge I guess.  https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API  https://github.com/github/fetch
Priority: -- → P1
Note that the request also isn't showing up in the netmonitor when the XHR filter is applied
Another example that uses fetch alongside an xhr request: http://jsfiddle.net/8kfr826j/
The fetch request shows up as 'other' in the netmonitor in this example
This demonstrates the problem in Brian's jsfiddle. But the worst problem is that I often don't want to see the noise of downloading lots of static assets, so normally I switch of "Log" under the Console tab. But I can't with fetch requests.
Comment on attachment 8680169 [details] [diff] [review] make Fetch requests show up as XHR in network monitor Change the network monitor to categorize Fetch requests as "XHR".
Attachment #8680169 - Flags: review?(vporof)
Attachment #8680169 - Flags: review?(vporof) → review+
Fix test URL -- worked locally but not in try.
Attachment #8680169 - Attachment is obsolete: true
You need to log in before you can comment on or make changes to this bug.