Microsoft Edge Developer

Hi, are you a web developer or designer?

“No, I just want to share feedback on Microsoft Edge.”

Please use the Feedback Hub (requires Windows 10) to submit your feedback in the Microsoft Edge category. This site is for web developer and designer feedback only. Other feedback will be closed without action.

“Yes, I’m a web developer or designer with feedback for the Microsoft Edge platform.”

Great! This site is where the Microsoft Edge team collects feature requests from the web developer and designer community in the categories listed to the right. For bugs on existing features, please log an issue on the Issue Tracker.

Your feedback will help us with planning and to better understand how web developers and designers are using the platform. Top standards-based feature requests will also be copied over to status.microsoftedge.com, where you can track its development status.

For the most actionable feedback, please search and up vote for existing suggestions before submitting a new suggestion, and create a separate suggestion per idea. Note that off topic or inappropriate suggestions may be moderated. The Microsoft Edge team will use suggestions as an important input, but there are several additional factors that inform the final roadmap.

A note from our lawyers: Please do not send any novel or patentable ideas, copyrighted materials, samples or demos which you do not want to grant a license to Microsoft. See the Terms of Service for more information.

How can we improve the Microsoft Edge developer experience?

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Vote for an existing idea (3)
  • or
  1. Fully implement the FormData API

    Currently the FormData API is only partially implemented in Edge. Most of the more useful methods are missing including: has(), get(), set(), delete(), entries(), and many others.

    FormData is already fully implemented on the other major browsers (Firefox, Chrome, Safari) - see: https://developer.microsoft.com/en-us/microsoft-edge/platform/catalog/?q=formdata

    176 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  JavaScript  ·  Flag idea as inappropriate…  ·  Admin →
  2. Unprefix and support all @viewport properties

    CSS Device Adaption (http://dev.w3.org/csswg/css-device-adapt) is partially supported through the @-ms-viewport rule, however the width and height property are the only ones supported. It would be nice if the zoom and orientation properties were supported, too (in addition to the rest of the spec), so that we'd get a real replacement for the non-standard viewport <meta> tag.

    39 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  CSS  ·  Flag idea as inappropriate…  ·  Admin →
  3. Support the '.displayName' property for the F12 developer tools

    Both Firefox and Safari support the '.displayName' property in their developer tools. Chrome has partial support (debugger - not yet profiler, but is working on it).

    This is crucial for many of us that have large codebases of anonymous Functions.

    A suggestion: over the years as this property has been added to the other browsers, the temptation has been to try to do some level of static analysis to determine Function names. In the end, this always fails to capture some use case given that JavaScript is incredibly flexible. Functions are Objects in JavaScript. A core idea in OO is…

    17 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Developer Tools  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Microsoft Edge Developer

Feedback and Knowledge Base