F12 tools don't always show failing requests

Fixed Issue #12810534


Antón M.
Jul 18, 2017
This issue is public.
Found in
  • Microsoft Edge
Found in build #
Fixed in build #
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

  1. Go to any site (www.bing.com for example)
  2. Open the F12 tools and go to the network tab
  3. Disable “Clear log on navigation”
  4. Disable network
  5. Go to another url (or do a search if in bing)


See a new entry in the network tab that should eventually fail


Nothing happens.


We are working on adding new features to edge diagnostics adapter in this PR and we are trying to implement the event Network.loadingFailed from the chrome debugging protocol but we do not receive OnResponseReceived when a request fails.


0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Hirsch S.”

    • To add some more information of the context, we are using the Windows.Web.Http.Diagnostics.HttpDiagnosticProvider class to receive the events from Edge. The code is here and we subscribe to the RequestResponseCompleted event:

      _requestResponseCompletedToken = _provider->RequestResponseCompleted += ref new TypedEventHandler(this, &HttpListener::OnRequestResponseCompleted);

      The issue is that we do not receive the RequestResponseCompleted event for requests when the network connection is down for instance.

    • Microsoft Edge Team

      Changed Assigned To from “Hirsch S.” to “Scott J.”

      Changed Assigned To from “Scott J.” to “Eric J.”

      Changed Status to “Confirmed”

      Changed Assigned To from “Eric J.” to “Duncan H.”

      Changed Status from “Confirmed” to “Fixed”

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

    Sign in