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.
-
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:
let objClone = { ...obj };
References:
312 votes -
ResizeObserver
A implementation of the ResizeObserver API would be nice.
Explainer: https://github.com/WICG/ResizeObserver/blob/master/explainer.md
Spec: https://wicg.github.io/ResizeObserver/Thanks!
50 votes -
Asynchronous Clipboard API
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…
19 votes -
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.
Example code: https://gist.github.com/bogas04/50eae983a9b478e172a22bb9fce9c77e
API Spec: https://wicg.github.io/web-share/
Explainer: https://github.com/WICG/web-share/blob/master/docs/explainer.md132 votes -
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
6 votes -
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.
67 votes -
RegExp Named Capture Groups
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.
5 votes -
Support BigInt
Please support BigInt, a stage-3 proposal. https://tc39.github.io/proposal-bigint/
3 votes -
IndexedDB 2.0
Full IndexedDB version 2.0 support!
90 votes -
"(input[type=file] element).files = dataTransfer.files" fails in Edge
We fail to pass "dataTransfer.files" of DragEvent to "files" property of the input[type="file"] element in Edge. For example:
HTML:
<input id="fileItem" type="file">Javascript:
var myfiles = dataTransfer.files;
document.getElementById('fileItem').files = myfiles; //This fails in Edge, but no errors are shown in consoleSteps to Reproduce a Bug:
https://jsfiddle.net/vth82jst/2/1. Drag & drop your file to input[type="file"] area
2. Check the "drop file name" and "input value"
3. Even if we drop a file, the "input value" does not change in Edge (It remains "ファイルは選択されていません" unchanged).I am troubled when I want to select files by drag & drop in Edge.
This…3 votes -
Background Fetch API
Implement Background Fetch API:
https://wicg.github.io/background-fetch/13 votes -
Implement worker modules
Allow workers to execute module scripts too.
Proposed spec:
https://github.com/whatwg/html/pull/608firefox bug:
https://bugzilla.mozilla.org/show_bug.cgi?id=1247687chromium bug:
https://bugs.chromium.org/p/chromium/issues/detail?id=68004675 votes -
support for RTCRtpSender.replaceTrack
ORTC introduced RTCRtpSender.replaceTrack as an alias for replaceTrack:
http://draft.ortc.org/#rtcrtpsender*This is currently not supported in Edge:
https://rawgit.com/aboba/edgertc/master/msortc-rs3.html#rtcrtpsender*The change was introduced in https://github.com/w3c/ortc/pull/661
7 votes -
Add support for brignToFront() on leaflet maps
Add support for brignToFront() for layers on leaflet maps.
Example of map where this function not working.
http://leafletjs.com/examples/choropleth/example.html1 vote -
WebVR : Add support for Oculus Rift, OpenVR and OSVR
WebVR is now supported by the latest version of Edge in the Creator Update and that's amazing. However, it is limited to Mixed Reality Devices and those devices and they are not available. Windows 10 users who already have a VR headset such as a Rift or a Vive, have to use a beta browser to enjoy WebVR.
Please considere to update Edge with at least a support for the Oculus Rift and the Vive. And only if you want to be a super hero, add OSVR support too.
239 votes -
support for constructing RTCRtpSender with 'kind' and without transport
Newer versions of the ORTC specification allow constructing RTCRtpSender with a ‘kind’ and make the transport argument optional:
http://draft.ortc.org/#rtcrtpsender*Edge only implements a version of the spec requiring a MediaStreamTrack and the transport:
https://rawgit.com/aboba/edgertc/master/msortc-rs3.html#rtcrtpsender*Supporting the current specification is required for shimming webrtc 1.0 ontop of ORTC. Currently I am working around this restriction with a javascript shim that does a lazy initialization of the native RTCRtpSender:
https://github.com/otalk/rtcpeerconnection-shim/pull/41(previously filed as https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/14627286/ )
1 vote -
Add support Shared Web Worker
Wee need single thread for all tabs for working with websocket.
Please add support Shared Web WOrker!87 votes -
Support the searchParams property of URL objects
Add support for the URLSearchParams interface (https://developer.mozilla.org/en-US/docs/Web/API/URLSearchParams) and the corresponding searchParams property of URL objects (https://developer.mozilla.org/en-US/docs/Web/API/URL/searchParams)
485 votesURLSearchParams has been implemented and will be included in an upcoming Windows 10 Insider Preview Build.
-
Web Bluetooth API with GATT support
We should be able to call the API's from Edge using JavaScript
38 votes -
Support "wheel" events for 2-finger scrolling on Precision Touch Pads (like every other browser does, and every other trackpad does)
Microsoft Edge is the only browser that doesn't support 2-finger scrolling properly. Sure, it scrolls the web page, but it doesn't fire wheel events. It instead just lets the OS handle it. This breaks critical functionality not only on the web, but also in many Windows 10 apps that are built using js/html (which is executed by the Edge engine). The biggest example is Flipboard, which doesn't let you "flip" through pages using the scroll gesture on the precision trackpad that Microsoft's own Hardware ships with (every Surface Pro / Book for the past 3+ years).
To verify the problem,…
344 votes
- Don't see your idea?