Microsoft Edge Developer

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

Vote for an existing idea ( )

Post a new idea…

Hot ideas

Top ideas

New ideas

Category

Status

My feedback

Support the `inert` attribute

Trapping focus in modal dialogs or preventing focus in background layers in modern web applications is extremely difficult and error-prone. Developers either have to walk the DOM and disable every focusable control with tabindex="-1" and `aria-hidden="true"` on a parent element, or do some tricky JavaScript to maintain focus inside of an element. Many developers get this wrong or they don't do it at all, creating horribly inaccessible experiences for keyboard and screen reader users.

The inert attribute currently being explored in the WICG solves this problem by providing a mechanism to disable entire subtrees in HTML. By setting `inert` on an HTML element, it renders every interactive control non-focusable and removes it from the accessibility tree.

Inert means no more walking of the DOM to set and restore tabindex, and forgetting to set `aria-hidden="true"` on a parent element (it happens all the time). The inverse also commonly occurs–developers set `aria-hidden="true"` on a parent element, and forget to modify tabindex on links and buttons, causing "ghost controls" with no accessibility information. Like I said, it's extremely error-prone. We need `inert` to make these scenarios much easier. It's a breeze in comparison! Set it on a sibling element to the one that remains visible, and you can handle focusability and AT access in one go.

The inert attribute currently being explored in the WICG solves this problem by providing a mechanism to disable entire subtrees in HTML. By setting `inert` on… more

Spread operator for object literals

This feature is currently Stage 3 and is implemented by Firefox stable, Chrome stable, Safari Preview, and Node stable.

This is really useful for shallow cloning objects:

object-fit and object-position for all media elements

Object-fit and object-position is defined for all visual media, not only for images, but also for video or canvas elements.

Implement Web Share API

Web Share API landed on Chrome for Android in version 61. It's a neat way of providing native sharing hooks to a web app.

Allow developers to disable script from F12

Useful for debugging and seeing what a no-JS or slow-JS experience might be like.

IndexedDB 2.0

Full IndexedDB version 2.0 support!

ORTC/WebRTC: add VP8 RTP PictureID

it seems that ORTC/WebRTC stack does not add VP8 RTP PictureID [1] which is needed by Switching Mixer Media Servers [2] to properly perform its rewriting when RTP flow switchings take place in order to avoid some issues in clients (eg: Chrome) that depend on it.

Could it be added as feature request?

Thanks in advance!!

support trickle ice

trickle ice support for webrtc

File API support for extensions

One great addition to Edge extensions would be the ability to write files .

There are of course security issues related to reading or writing files to the file system, but at some point, Edge will support the Downloads API (6 out of the 20 most popular Firefox extensions rely on this API). This API (chrome.downloads) allows to write a file to the Downloads folder out of an external URL. Why not then allow an extension to generate files limited to that folder ?

That would allow saving videos (some streaming protocols need processing so the Downloads API is not sufficient), screenshots, browsing session records, .

To be useful, this API would need real binary data write/seek ability, not a simple blob-to-file feature.

This would make Edge ahead of Chrome as this ability is deeply lacking in that later browser.

One great addition to Edge extensions would be the ability to write files .

That would allow saving videos (some streaming protocols need processing so the Downloads API is not… more

Variable Open Type Fonts

Variable Open Type fonts are an important innovation in font distribution and loading performance, in that a single font can be configured to render and replace many different weights (among other configuration axes).

Implement worker modules

Allow workers to execute module scripts too.

Display: contents

Display: contents is incredibly useful when working with grid and flexbox. It is already implemented in Firefox and works really well.

It allows ancestors that are not direct children to become flex-items or grid-items.

Microsoft Edge does not support page linking in internal PDF viewer

Microsoft Edge does not support page linking in internal PDF viewer.

In Chrome and Firefox you can jump straight to a page with a URL Hashtag suffix.

For example, to jump straight to page 9 of this Microsoft PDF, adding "#page=9" will take you directly there in Chrome/Firefox.

However Microsoft Edge does not support this feature.

As a **developer**, I have pages coded to link to specific pages in PDFs that are up to 1,300 pages long. this is really frustrating for our end users.

Add support for CSS prefers-reduced-motion media feature.

New in CSS Media Queries Level 5:

WebKit blog post covering the feature, justification, and examples:

Suport "appearance: none" for

Would be nice if Edge supports appearance (or -webkit-appearance) set as 'none' for elements, like radio or checkbox.

RTC Data Channels

Data channels allow a web application to send and receive generic application data peer-to-peer.

This feature request is specifically about the *data channel* component of the WebRTC specification. This is separate from Object RTC and WebRTC 1.0 feature requests because the Platform Status site breaks out data channels separately.

RTC Data Channels:

Uservoice: (this ticket)

Downloads API support for extensions

Missing Downloads API support is not good. I wanted to port my extension but it relies on basic downloads API missing in Edge.

Implement CSS `display: flow-root` (modern clearfix)

`display: flow-root` is a modern way to force a block to be a formatting context that floated elements are contained in (aka clearfix).

From the spec [1]:

> The element generates a block container box, and lays out its contents using flow layout. It always establishes a new block formatting context for its contents.

Tab Atkins and Elika Etemad (fantasai) from CSSWG consider the feature stable enough to be implemented [2].

OffscreenCanvas

From MDN: The OffscreenCanvas interface provides a canvas that can be rendered off screen. It is available in both the window and worker contexts.

From me: It would be great to prepare images and run WebGL without tying up the UI thread.

Async Generators / Async Iterators

Async iterators and async generator functions(https://github.com/tc39/proposal-async-iteration) are now a stage-3 ECMAScript proposal, nearly finished. They make many styles of programming in JavaScript easier (https://ponyfoo.com/articles/javascript-asynchronous-iteration-proposal); in particular, they are important for WHATWG Streams (https://streams.spec.whatwg.org). As of 2017-10-22, async generators have already been implemented in Blink, Firefox, and WebKit.

Don't see your idea?

Post a new idea…

New and returning users may sign in