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.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. DNS over https

    we need support for DNS over HTTPS and TLS

    63 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Networking  ·  Flag idea as inappropriate…  ·  Admin →
  2. 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:

    Platform status: https://developer.microsoft.com/en-us/microsoft-edge/platform/status/rtcdatachannels/?q=data%20channels
    Uservoice: (this ticket)

    Object RTC:

    Platform status: https://developer.microsoft.com/en-us/microsoft-edge/platform/status/webrtcobjectrtcapi/?q=Object%20RTC
    UserVoice: https://wpdev.uservoice.com/forums/257854-microsoft-edge-developer/suggestions/6263666-webrtc-object-rtc-api

    WebRTC 1.0:

    Platform status: https://developer.microsoft.com/en-us/microsoft-edge/platform/status/webrtcwebrtcv10api/?q=WebRTC
    UserVoice: https://wpdev.uservoice.com/forums/257854-microsoft-edge-developer/suggestions/6508336-webrtc-webrtc-v1-0-api

    3,752 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    21 comments  ·  Networking  ·  Flag idea as inappropriate…  ·  Admin →
  3. Allow URIs max length with query strings to be at minimum 8,000 octets

    (I believed URIs and request-lines are part of networking. If this is not true, please move this to the correct category.)

    Currently, Microsoft Edge supports up to 4,035 octets in the URIs with query strings, or somewhere around that length. Chromium-based browsers can handle up around 8,000 octets in the URIs with query strings.

    I don't know if the information above is based on the RFC7230, Section 3.1.1, where they defined that request-lines and URIs max length to be at least 8,000 octets long at minimum or if the fact it is based around the max length determined from there.…

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Networking  ·  Flag idea as inappropriate…  ·  Admin →
  4. RTSP Streaming Protocol Support

    The video surveillance industry relies heavily on the RTSP protocol (as implemented by ffmpeg, vlc media player, live555, etc) for streaming h264 and h265 video content.

    It's not a new protocol by any stretch but it is part of the ONVIF standard that essentially all video surveillance manufacturers use as well as part of the PSIA standard which a subset of the manufacturers also support (in addition to ONVIF).

    It's a simple protocol and there are plenty of open source implementations.

    HTML5 does not include equivalent functionality.

    WebRTC pushes VP8/9 and while it may support h264 it's often online baseline…

    23 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Networking  ·  Flag idea as inappropriate…  ·  Admin →
  5. Will Edge support QUIC protocol introduced by Google?

    Will Edge support QUIC protocol introduced by Google?

    25 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Networking  ·  Flag idea as inappropriate…  ·  Admin →
  6. Websocket - support for custom headers for handshake

    please consider adding ability to add custom headers for handshake. In RFC6455 there one interesting point:

    The request MAY include any other header fields, for example, cookies [RFC6265] and/or authentication-related header fields such as the |Authorization| header field [RFC2616], which are processed according to documents that define them. I've found an example how to add custom header to handshake: https://blog.heckel.xyz/2014/10/30/http-basic-auth-for-websocket-connections-with-undertow/ but this is for Java and unfortunately isn't possible in HTML5.

    When searching over the net I found many places question about this option, for example: sta/websocket-sharp#22 https://stackoverflow.com/questions/4361173/http-headers-in-websockets-client-api/4361358#4361358 aspnet/SignalR#888

    For example in Python this is possible https://stackoverflow.com/questions/15381414/sending-custom-headers-in-websocket-handshake. Other languages…

    17 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Networking  ·  Flag idea as inappropriate…  ·  Admin →
  7. SSL key logging (aka SSLKEYLOGFILE)

    SSL key logging is a feature that browsers export TLS keys into a text file, which can be used by Wireshark to decrypt TLS traffic. This feature can be enabled on Firefox and Chrome by setting SSLKEYLOGFILE environment variable, which is a path to the log file.

    This feature is useful for debugging network error and for learning structures of TLS-encrypted application layer protocols (such as encrypted HTTP/2) with Wireshark.

    See also:
    [1] https://developer.mozilla.org/en-US/docs/Mozilla/Projects/NSS/Key_Log_Format
    [2] https://wiki.wireshark.org/SSL#Using_the_.28Pre.29-Master-Secret

    118 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Networking  ·  Flag idea as inappropriate…  ·  Admin →
  8. 1,398 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    61 comments  ·  Networking  ·  Flag idea as inappropriate…  ·  Admin →
  9. Server-Sent Events (EventSource)

    Enables push notifications from the server received as DOM events.

    http://dev.w3.org/html5/eventsource/

    7,019 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    130 comments  ·  Networking  ·  Flag idea as inappropriate…  ·  Admin →
  10. HTTP Client Hints

    Header for proactive content negotiation; just as the Accept header allowed clients to indicate what formats they prefer, Client Hints allow clients to indicate a list of device and agent specific preferences.

    Spec: http://tools.ietf.org/html/draft-grigorik-http-client-hints

    645 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Networking  ·  Flag idea as inappropriate…  ·  Admin →
  11. Ajax caching working like other browsers

    Internet Explorer caches ajax responses too agressively. In the modern SPA world, everything is working through AJAX request, so it is more and more important, to not cache automatically all of the AJAX responses. Firefox and Chrome is working normal with AJAX responses, only IE caches too agressively.

    89 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Networking  ·  Flag idea as inappropriate…  ·  Admin →
  12. Navigation Error Logging

    This specification defines an interface to store and retrieve error data related to the previous navigations of a document.

    https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/NavigationErrorLogging/Overview.html

    101 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Networking  ·  Flag idea as inappropriate…  ·  Admin →
  13. Karaoke Web Standard

    Provides semantic language processing for two-way communication with a remote host. This new interface creates a system-to-system forced sonic recognition on the receiving party.

    https://pages.adrianba.net/karaoke/

    80 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Networking  ·  Flag idea as inappropriate…  ·  Admin →
  14. 3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Networking  ·  Flag idea as inappropriate…  ·  Admin →
  15. Edge caching could be improved in error cases

    I'm a developer on Azure CDN. When testing out some scenarios on our side, we noticed a difference in behavior between how Chrome browser and Edge browser work for caching some bad responses. In our CDN, if we detect that the eTag on an 'If-None-Match' request header is for a 'malformed eTag' (one with no quotes), such as If-None-Match: 64988f77337209c5a7157a016c456d02, we return a 400 response.

    On chrome, the workflow goes like this:
    Download page, get 200, everything fine.
    Refresh page, browser sends If-None-Match with bad eTag, we detect this and send 400 to browser. Chrome detects this issue, and next…

    14 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Networking  ·  Flag idea as inappropriate…  ·  Admin →
  16. 103 Early Hints

    The 103 Early Hints status code allows a server to tell browsers what to pre-fetch (with link headers) before the final response is available (e.g. because the server needs to "think", or because it's fetching something from another server).

    This is functionally similar to HTTP/2 server push, but simpler and more interoperable.

    - Specification: https://tools.ietf.org/html/rfc8297
    - Firefox: https://bugzilla.mozilla.org/show_bug.cgi?id=1407355
    - Chrome: https://bugs.chromium.org/p/chromium/issues/detail?id=671310

    15 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Networking  ·  Flag idea as inappropriate…  ·  Admin →
  17. 3DES only available for local domains/router segments/local networks if needed. NOT FOR THE INTERNET.

    SCHANNEL : The 3DES Cipher should be used - if needed at all - ONLY selectively and definitely kept blocked - disabled - for Internet Connections ranging outside of a local Network boundary (or outside of proxied Segments or NAT Domains or also when not being used through either encrypted VPN Tunnels).
    I recommend this because it is weak. (64bit ciphers are generally considered weak now because of their limitation).

    43 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Networking  ·  Flag idea as inappropriate…  ·  Admin →
  18. Send window inner dimensions and screen DPI to the server with every request

    This is not a thing at the present time in any browser AFAIK, but wouldn't it be magical if SSR code could know exactly how many pixels it needs to render? We could optimize image sizes, we could try to render fonts server side, we could execute media/viewport queries and know the meanings of %-based layouts all before the page even makes it to the client. We could also compute layout on the server and decide to fetch less data (only above the fold for example) for smaller screens during initial page load. I'm surprised we haven't done this a…

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Networking  ·  Flag idea as inappropriate…  ·  Admin →
  19. UI interface for dns resolving

    I understood that because edge runs in a sandbox, it has problems using the hosts file.

    Maybe we can have an u.i. where we can set where the domains have to resolve to. So we don't need the hosts file anymore.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Networking  ·  Flag idea as inappropriate…  ·  Admin →
  20. Link Drug&Drop in panel in new tab and link Drug&Drop to panel in current tabs.

    Please add function drag and drop link to tabs panel and create new tabs or open link current tabs.

    9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Networking  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3
  • Don't see your idea?

Microsoft Edge Developer

Feedback and Knowledge Base