Fetch API Generates TypeMismatchError Instead of TypeError

Fixed, flighted Issue #7528873

Details

Author
Kagami R.
Created
May 11, 2016
Privacy
This issue is public.
Found in
  • Microsoft Edge
Found in build #
14.14342
Fixed in build #
15016
Reports
Reported by 4 people

Sign in to watch or report this issue.

Steps to reproduce

  1. Type fetch("https://microsoftedge.com").catch(e => console.error(e))
  2. See DOMException TypeMismatchError.

MDN says TypeMismatchError is deprecated, BTW.

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Rob T.”

    • That specific line does not throw TypeMismatchError on 14352, but fetch("https://example.com").catch(e => console.error(e)) still does.

    • Microsoft Edge Team

      Changed Assigned To from “Rob T.” to “Brad E.”

    • In 14386 I am showing this as fixed.  Can you confirm that this is true for me, please?

      Best regards,
      The MS Edge Team

    • Yes for same-origin URLs, no for non-same-origin ones. (build 14388)

      fetch("https://github.com").catch(e => console.error(e)) still gives me TypeMismatchError when it should be NetworkError.

    • Microsoft Edge Team

      Changed Assigned To to “Venkat K.”

      Changed Assigned To from “Venkat K.” to “Brandon M.”

      Changed Title from “Fetching HTTPS content is always being rejected with type mismatch error” to “Fetch API Generates TypeMismatchError Instead of TypeError”

      Changed Status to “Confirmed”

      Changed Status from “Confirmed” to “In code review”

      Changed Status from “In code review” to “In progress”

      Changed Status from “In progress” to “In code review”

    • NetworkError rather than TypeError right? (I didn’t set the title, a Microsoft person did.)

    • Microsoft Edge Team

      Changed Status from “In code review” to “Fixed, not yet flighted”

    • To clarify, TypeError is used in the spec, Firefox, and Chrome in this case. We have fixed the issue and it should be available in an upcoming insider build. Thank you!

    • Microsoft Edge Team

      Changed Status from “Fixed, not yet flighted” to “Fixed, flighted”

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

    Sign in