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 CSS 'overscroll-behavior'

    Consider implementing the new CSS overscroll-behavior property.

    ## Specification
    This feature specification is being incubated in WICG:
    https://wicg.github.io/overscroll-behavior/

    Additional background on this feature may be found here:
    https://github.com/w3c/csswg-drafts/issues/769

    ## Summary
    CSS overscroll-behavior standardizes a supercharged version of "-ms-scroll-chaining". It allows developers to determine the browser's behavior once a scroller has reached its full extent.
    The unused delta can be propagated to the parent causing scroll chaining, create a glow/bounce effect without chaining, or just get consumed silently. In particular when used on viewport defining element, it controls if overscroll can be used for navigation actions such as pull-to-refresh or swipe…

    127 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  CSS  ·  Flag idea as inappropriate…  ·  Admin →
  2. Implement allow-popups-to-escape-sandbox token for iframe sandbox attribute

    Implement the token allow-popups-to-escape-sandbox for the iframe's sandbox attribute, as described here: https://html.spec.whatwg.org/multipage/embedded-content.html#attr-iframe-sandbox. It has use cases for things like maps and advertising publishing.

    79 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  HTML  ·  Flag idea as inappropriate…  ·  Admin →
  3. Auto Update Older IE Versions

    Force older versions of Internet Explorer to automatically update.

    7,550 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    62 comments  ·  Miscellaneous  ·  Flag idea as inappropriate…  ·  Admin →

    On December 15th of 2011 Microsoft made a big change that largely goes unnoticed by the vast majority of users; updates to Internet Explorer began to happen automatically.

    Today, Microsoft continues to install the latest updates for Internet Explorer supported by the user’s operating system without getting in the way. With Internet Explorer 10 we also added a UI control to the “About Internet Explorer” window which gave the end-user easier control over this process.

    Understandably there are some situations in which auto-updates are not desired. For instance, enterprise customers may (and do) choose to opt-out of these updates due to a reliance upon older versions of Internet Explorer internally.

    Tasked with supporting legacy applications, while also supporting the advancing web, the Internet Explorer team developed Enterprise Mode for Internet Explorer 11. This feature is designed to grant the user all of the security and speed of a modern browser,…

  4. 5,159 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    41 comments  ·  Media  ·  Flag idea as inappropriate…  ·  Admin →
  5. CSS Masking

    Allows hiding of portions of a visible elements.

    Spec: https://dvcs.w3.org/hg/FXTF/raw-file/tip/css-masking-1/index.html

    2,368 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    36 comments  ·  CSS  ·  Flag idea as inappropriate…  ·  Admin →
  6. 2,148 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    55 comments  ·  HTML  ·  Flag idea as inappropriate…  ·  Admin →
  7. Drag and Drop Directories

    Allows dragging and dropping entire folders using HTML5 Drag and Drop. Extends the DataTransferItem with a method to get a FileEntry/DirectoryEntry.

    Spec: http://wiki.whatwg.org/wiki/DragAndDropEntries

    801 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    8 comments  ·  HTML  ·  Flag idea as inappropriate…  ·  Admin →
  8. indexedDB explorer in dev-tools

    It would be nice to see the indexedDB database in dev-tools.
    Think about:
    * Version
    * ObjectStores
    * Data in objectstores
    * Indexes for objectstores

    336 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Developer Tools  ·  Flag idea as inappropriate…  ·  Admin →
  9. iframe[srcdoc] attribute

    Gives the content of an iframe as a src context to embed (e.g. <iframe seamless srcdoc="<b>Hello World</b>"></iframe>).

    Spec: http://www.w3.org/html/wg/drafts/html/master/embedded-content.html#attr-iframe-srcdoc

    355 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    working on it  ·  3 comments  ·  HTML  ·  Flag idea as inappropriate…  ·  Admin →
  10. Support the Encoding API

    Namely TextEncoder and TextDecoder

    Spec: https://encoding.spec.whatwg.org

    201 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  JavaScript  ·  Flag idea as inappropriate…  ·  Admin →
  11. Don't treat ms-browser-extension:// as mixed content

    If an extension wants to inject its own UI into an iframe on a https page, it should not be blocked with the error message "SEC7111: HTTPS security is compromised by ms-browser-extension://..."

    25 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Extensions  ·  Flag idea as inappropriate…  ·  Admin →
  12. Extension background page should be debuggable

    The background page of an extension should be debuggable, or there should at least be a way to see the unhandled JavaScript exceptions thrown and console.log calls by the background page.

    13 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Extensions  ·  Flag idea as inappropriate…  ·  Admin →
  13. Support SVG 2 paint-order property

    The SVG 2 paint-order property allows authors to control the order in which stroke, markers, and fill are painted for each shape, or for text. This can be used to create outlines that do not obscure fine details of shapes or text. It can also be used to create more subtle line markers that do not obscure the line itself.

    The basic fill/stroke/markers options, as defined in the current draft of the specification, are already supported in Firefox, Chromium, and Webkit. They are therefore unlikely to change, although additional options may be added by future specifications.

    http://www.w3.org/TR/SVG2/painting.html#PaintOrder

    55 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Graphics  ·  Flag idea as inappropriate…  ·  Admin →
  14. Remove whatever the character limit is on Console.log

    The arbitrary limit on the length of characters that can be sent to console in a single statement seems to have persisted from IE.

    Remove it. Just because long logs isn't best practice doesn't mean a limit should be enforced. It simple makes Edge unusable for debugging those apps.

    28 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Developer Tools  ·  Flag idea as inappropriate…  ·  Admin →
  15. W3C Manifest support

    Add support for the new W3C manifest specification for pinned apps as well as for Windows store applications.

    The spec allows for vendor extensions which can be used for things missing in the Level 1 of the spec. A lot of things have already been planned for Level 2 so it would be great if the MS team could participate in the discussions

    783 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  HTML  ·  Flag idea as inappropriate…  ·  Admin →
  16. F12 Support for web browser and web view controls

    Currently there are no production tools to debug web browser (.NET) or web view (Store App) applications. It is nightmare to identify JavaScript memory leaks and sometimes hang and crash as well. Ability to troubleshoot them (post mortem analysis) would go long way.

    19 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Developer Tools  ·  Flag idea as inappropriate…  ·  Admin →
  17. Debug for Edge on mobile/Xbox/RaspberryPi

    Just like it happens for OSX/iOS, where attaching a device via USB or connecting via wifi allows to use desktop safari to inspect mobile safari and webviews on the mobile. All other browsers support this but Edge.

    I know weinre was recently adapted to be usable on Edge mobile too but it's hardly a complete solution for serious development, lacking support for breakpoints, CSS pseudo-element.

    Not to mention that I did encounter really strange behaviors of the DOM inspection panel based on when the weinre resources are loaded during JavaScript execution, something that is not acceptable to develop modern SPA…

    592 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    10 comments  ·  Developer Tools  ·  Flag idea as inappropriate…  ·  Admin →
  18. Change development cycle for frequent updates

    IE falling behind before it was released. All major browsers has release cycles less than IE has between announcement and release.
    Also, old version do not get updates.
    Drop version from name and start actively supporting IE.

    378 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Miscellaneous  ·  Flag idea as inappropriate…  ·  Admin →
  19. Make the Escape key open the console when using the F12 tools

    This keyboard shortcut just seems to make sense to me and matches what Chrome and Firefox do. CTRL+` doesn't feel as obvious.

    36 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Developer Tools  ·  Flag idea as inappropriate…  ·  Admin →
  20. setDragImage on dataTransfer of DragEvent

    This has been overlooked sine IE 5.5, it has even made it way to the mobile IE (http://caniuse.com/#feat=dragndrop) but not the desktop one.

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

Microsoft Edge Developer

Feedback and Knowledge Base