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. Implement DOM4 methods: prepend(), append(), before(), after() and replaceWith()

    Steps to reproduce the problem:
    1. Open the testcase http://jsbin.com/fiqacod/edit?html,js,output in Edge.

    What is the expected behavior?
    The test should pass.

    What went wrong?
    The test failed, indicating that Edge does not support the relevant DOM4 methods.

    Specification: https://dom.spec.whatwg.org/#interface-childnode
    Chrome Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=255482
    Firefox Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=911477
    Can I Use: http://caniuse.com/#feat=dom-manip-convenience

    278 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Document Object Model (DOM)  ·  Flag idea as inappropriate…  ·  Admin →
  2. Update CSS Grid

    Update the IE implementation of Grid Layout to match the current spec. The current implementation from the IE 10 days is outdated.

    8,721 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    258 comments  ·  CSS  ·  Flag idea as inappropriate…  ·  Admin →
  3. Support Web Worker creation via blob URLs

    Currently in Firefox and Chrome you can create a new Worker() using JavaScript defined as a Blob URL. In IE and Edge, you cannot.

    This Blob trick is very convenient, because it allows JavaScript libraries to seamlessly expose WebWorker functionality, without having to require users to build two separate scripts.

    Currently there are workarounds, but they're hacky and based on the unsafe eval(): https://github.com/padolsey/operative#no-worker-via-blob-support

    38 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Miscellaneous  ·  Flag idea as inappropriate…  ·  Admin →
  4. CSS Variables

    Introduces cascading variables as a new primitive value type that is accepted by all CSS properties, and custom properties for defining them.

    Spec: http://www.w3.org/TR/css-variables/

    5,870 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    57 comments  ·  CSS  ·  Flag idea as inappropriate…  ·  Admin →
  5. position: sticky

    position: sticky is a new way to position elements and is conceptually similar to position: fixed. The difference is that a stickily positioned element behaves like position: relative within its parent, until a given offset threshold is met.

    Spec: http://dev.w3.org/csswg/css-position/#sticky-pos

    4,649 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    14 comments  ·  CSS  ·  Flag idea as inappropriate…  ·  Admin →
  6. Subresource Integrity

    Subresource Integrity defines a mechanism by which user agents may verify that a fetched resource has been delivered without unexpected manipulation. In a nutshell, metadata inlined into HTML elements allows the browser to determine whether the resource that was downloaded matches the resource the page's author expected to download.

    http://w3c.github.io/webappsec/specs/subresourceintegrity/

    2,412 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    42 comments  ·  Networking  ·  Flag idea as inappropriate…  ·  Admin →
  7. 1,608 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    33 comments  ·  HTML  ·  Flag idea as inappropriate…  ·  Admin →
  8. Cookie inspection and editing

    This feature would allow the inspection and modification of all cookies relevant to the current page via a tabular view in F12.

    Proposed Design
    - New item in file picker "Cookies"
    - Once opened all cookies relevant to the page (based on top URL) will be displayed in a grid with columns for; name, value, domain, path, expires time, HTTP (only), Secure (only)
    - Grid is fully editable
    - Options to clear all cookies and session cookies

    61 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    9 comments  ·  Developer Tools  ·  Flag idea as inappropriate…  ·  Admin →

    In Edge cookies are now show in the file picker of the F12 debugger. To see cookies just open F12, go to the debugger and open the file picker (ctrl+o or folder icon) and you will see a folder node for cookies under which each will be a number of nodes for each page. Clicking on the node will open up a grid view of all the cookies relevant to that page the grid is editable so cookies can be updated and deleted.

  9. Provide MD5 hashes/checksums for current moden.ie test VMs

    I maintain some scripts to do automatic, headless testing of our web apps on Internet Explorer using your wonderful VMs from the modern.ie portal.

    Currently the workflow of the testing is split apart in two major phases:
    1. An integration testing platform that takes a customized modern.ie VM and opens IE and runs some automated, headless tests of our web application after each successful build.
    2. A meta-script that downloads a VM from the modern.ie portal and runs some additional customizations (such as adding internal certificates, etc.) needed by our testing platform. This meta script then exports the customized VM…

    1 vote
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Developer Tools  ·  Flag idea as inappropriate…  ·  Admin →

    You can use the following endpoint:
    https://developer.microsoft.com/en-us/microsoft-edge/api/tools/vms/

    This is the JSON we use to know what to download and contains the links to everything. The links to the VMs change each time there is a new version. E.g.:

    https://az792536.vo.msecnd.net/vms/VMBuild_20180425/Parallels/MSEdge/MSEdge.Win10.Parallels.zip

    VMBuild_20180425 is the part that will change.

    The JSON also has links to the sums of each file if you are interested.

    Hope this helps!

  10. Add feature detection for iframe sandbox tokens

    Add the ability for developers to determine support for sandbox tokens and react accordingly. For example:

    var iframe = document.createElement('iframe');
    if (iframe.sandbox.supports('allow-popups-to-escape-sandbox')) {
    alert('support tp');
    }

    15 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  HTML  ·  Flag idea as inappropriate…  ·  Admin →
  11. Support CSS hyphens property

    The `hyphens` CSS property allows the author to request automatic hyphenation, or to manually insert soft hyphens to explicitly indicate hyphenation opportunities, or to turn off hyphenation. https://developer.mozilla.org/en-US/docs/Web/CSS/hyphens

    As of EdgeHTML 16, the ePub viewer inserts automatic hyphens, but with no control (resulting in hyphens where there shouldn't be, like in code). The normal web view uses soft hyphens for manual hyphenation (the default CSS behavior), but does not have automatic hyphenation support. The `hyphens` property is not recognized at all.

    16 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  CSS  ·  Flag idea as inappropriate…  ·  Admin →
  12. 252 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Performance  ·  Flag idea as inappropriate…  ·  Admin →
  13. 3 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  HTML  ·  Flag idea as inappropriate…  ·  Admin →
  14. Support Screen Capture per W3C Specification

    The Screen Capture (or screen share) specification [1] allows websites to obtain a MediaStream of the user's screen, given permission from the user.

    Firefox has implemented the feature per specification (no longer requiring a whitelist [2]), while Chrome only allows the feature when initiated from an extension.

    [1] Specification: https://www.w3.org/TR/screen-capture/

    [2] Firefox re:whitelisting: https://wiki.mozilla.org/Screensharing

    54 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. Internet Explorer / Edge Changelog

    Provide high-level and detailed Internet Explorer 7 Edge Version change log: with the new Windows servicing model my customers are moving away from full-stack management and related full test cycles - in order to assess the potential impact of the changes it would be beneficial to get access to the above mentioned information

    1 vote
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Miscellaneous  ·  Flag idea as inappropriate…  ·  Admin →
  16. Implement 'once' event listener option

    The DOM Standard defines a 'once' option for addEventListener() which causes the callback to only be called once, upon the next occurrence of the given event type, after which the listener gets automatically removed:
    https://dom.spec.whatwg.org/#dom-addeventlisteneroptions-once

    The effect is similar to jQuery's popular $.one() method.

    CanIUse entry: http://caniuse.com/#feat=once-event-listener
    MDN article: https://developer.mozilla.org/en-US/docs/Web/API/EventTarget/addEventListener#Parameters

    159 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Document Object Model (DOM)  ·  Flag idea as inappropriate…  ·  Admin →
  17. Support "SameSite" cookie option

    The "SameSite" cookie prevents CSRF attacks by telling the browser not to send the cookie in requests that originate from sites other than the one that created it.

    Read the spec draft here:

    https://tools.ietf.org/html/draft-west-first-party-cookies-07

    Chrome already supports it as declared here:

    https://www.chromestatus.com/feature/4672634709082112

    450 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Security  ·  Flag idea as inappropriate…  ·  Admin →
  18. 3 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Document Object Model (DOM)  ·  Flag idea as inappropriate…  ·  Admin →
  19. dashlane support

    Dashlane claims edge does not support a certain feature to enable them to write a plugin:
    https://csdashlane.zendesk.com/hc/en-us/articles/202699161-Request-Dashlane-on-a-Platform-or-Browser

    Please do whatever is needed to get dashlane working on edge, it's really in excusable to not have such a popular app supported. I would then use edge immediately, thank you

    57 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Extensions  ·  Flag idea as inappropriate…  ·  Admin →
  20. 485 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    10 comments  ·  JavaScript  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5 9 10
  • Don't see your idea?

Microsoft Edge Developer

Feedback and Knowledge Base