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".

Enter your idea

(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.

Pretty print no longer works with large JS files in the latest updates. I thought it was completely broken, but for small files it works fine. Please fix, this is making hard to justify using Edge when I can't debug.

Use case: A stable sort is really important for browsers because so much of what they're sorting is for UI display purposes. Users don't like it when sorting a grid by a certain column and "equal" rows randomly resort if the grid decides to resort them.

The clipboard spec now has an asynchronous API [2] which is significantly more ergonomic than past clipboard APIs – it avoids various issues that the old document.execCommand("copy") approach had, and is much easier to use:

navigator.clipboard.writeText("hello world").then(...);

IE 9/10/11 shipped an unstandardized API for copying text or URLs to the clipboard. Edge shipped an older version of the draft standard clipboard/editing-spec-based-API [1], but it has numerous bugs and inconsistencies [2] that even *make it impossible to tell if the attempted copy action has succeeded*. Existing bugs aren't seeing attention, and it seems likely to me that there are more undiscovered bugs due to baggage of the abandoned editing spec [3].

I maintain a library where I try work around the Edge bugs, but it would be better for developers if they could use the simple asynchronous API directly, at least for copying plain text.

The clipboard spec now has an asynchronous API [2] which is significantly more ergonomic than past clipboard APIs – it avoids various issues that the old document.execCommand("copy") approach had, and is much easier to use:

navigator.clipboard.writeText("hello world").then(...);

IE 9/10/11 shipped an unstandardized API for copying text or URLs to the clipboard. Edge shipped an older version of the draft standard clipboard/editing-spec-based-API [1], but it has numerous bugs and inconsistencies [2] that even *make it impossible to tell if the attempted copy action has succeeded*. Existing bugs aren't seeing attention, and it seems likely to me that there are more undiscovered…

The proposal is in Stage 4, so it will be included in next ECMAScript release. Chrome and Safari have implemented this feature for regular expression. Named groups make regex easier to read when there are many groups.