Implement URLSearchParams

Fixed Issue #8993198


paul i.
Sep 20, 2016
This issue is public.
Found in
  • Microsoft Edge
  • Internet Explorer
Fixed in build #
Reported by 31 people

Sign in to watch or report this issue.

Steps to reproduce

Try to run this:

var paramsString = “q=URLUtils.searchParams&topic=api”
var searchParams = new URLSearchParams(paramsString);



0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Ibrahim O.”

      Changed Assigned To to “Travis L.”

      Changed Status to “Confirmed”

      Changed Assigned To from “Travis L.” to “Jeff W.”

    • Is there an update as to when Microsoft IE 11 and Edge will support the URLSearchParams?

    • Microsoft Edge Team

      Changed Steps to Reproduce

    • Edge and IE11 are falling behind in this field. Lots of Angular, ReactJS and Vue.js devs like to use it:

    • Microsoft Edge Team

      Changed Assigned To from “Jeff W.” to “Allison P.”

    • Any news on when this will work?

    • Now that Angular is using URLSearchParams the lack of Edge support is really starting to be painful. Can anyone provide a timeline for when it’s going to be introduced?

    • Sorry about not replying to this sooner, I must have been missing the notifications.  This won’t be in the upcoming Fall Creators Update, but we hope to get it done in the release after that.

    • Microsoft Edge Team

      Changed Steps to Reproduce

    • Any updates on this?

    • Microsoft Edge Team

      Changed Status from “Confirmed” to “Fixed”

    • URLSearchParams has just been implemented. It will be included in a Windows Insider build in the near future. 

    • A recent update to seems to break the site for me. It’s using urlsearchparams. would be great to see this flighted soon.

    • Yes, please, ship it ASAP!

    • As of March 31 2018 the issue still exists. The issue was created on Sep 20 2016. Waiting for 2nd anniversary Microsoft Edge Team?

    • Edge 42 preview fixed this, probably it will be released next month.

    • (EdgeHTML 17)

    • Amazing that this issue still exists. I could understand if it would break backward compability - but that does not seem to be the case?

    • The patch is now in Release Preview ring (build 17133).

    • Great that this is fixed. Look forward to the new build.

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

    Sign in