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.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Feature request: Auto-resize iframes based on content

    After the recent removal of the `@seamless` attribute on the `<iframe>` from the WHATWG spec:

    https://github.com/whatwg/html/issues/331

    We still need to consider the problem of setting the height of iframes, so they contain their content without scroll bars.

    As discussed at:

    https://github.com/whatwg/html/issues/555
    https://lists.w3.org/Archives/Public/www-style/2016Jan/0236.html
    https://lists.w3.org/Archives/Public/www-style/2016Feb/0004.html

    The solution may simply involve the CSS:

    #iframe { height: max-content; }

    And a header on the framed content, rather than custom/buggy JavaScript.

    25 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  CSS  ·  Flag idea as inappropriate…  ·  Admin →
  2. Feature request: Animating max-height / height based on content

    When creating a disclosure widget:

    <p><a href="#widget">Show Terms &amp; Conditions</a></p>
    <div id="widget">
    <p>Long legal text, hidden by default.</p>
    </div>

    Developers used to use jQuery to display the hidden content with a height changing animation (so the content did not suddenly appear):

    $('#widget').slideToggle();

    More recently we have been using CSS animations:

    #widget {
    overflow-y: hidden;
    max-height: 500px; /* approximate max height */
    transition-property: all;
    transition-duration: .5s;
    }

    #widget.closed {
    max-height: 0;
    }

    https://davidwalsh.name/css-slide

    Where `max-height` has to be guessed (not too high, as the animation will be too fast, and not too small, as content will be unreadable).

    So can we…

    13 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  CSS  ·  Flag idea as inappropriate…  ·  Admin →
  3. 150 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 →
  4. Background-image transition

    The feature of setting transition for background-image will stop the mess with duplicate div's and z-index-opacity magic.
    Please make transitions available even W3C don't want it.

    Vote for transition: background-image!

    10 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  CSS  ·  Flag idea as inappropriate…  ·  Admin →
  5. Stop treating cursor: auto like cursor: inherit

    Currently in IE11 and MS Edge 1, cursor: auto is treated like cursor: inherit. Example:

    <div class="outer">
    <div class="inner">
    Text
    </div>
    </div>

    .outer{
    cursor: pointer;

    .inner {
    cursor: auto;
    }
    }

    If I hover over "Text", I get a pointer instead of the correct cursor (which should be the "text" cursor).

    More on this:

    http://stackoverflow.com/questions/21702643/opera-ie-cursor-auto-doesnt-work

    102 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  CSS  ·  Flag idea as inappropriate…  ·  Admin →
  6. :matches()

    Implement this helpful selector. WebKit and Mozilla have early implementations defined as :-prefix-any(), and the specification has been stable on this for quite some time.

    http://www.w3.org/TR/selectors4/#matches

    140 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  CSS  ·  Flag idea as inappropriate…  ·  Admin →
  7. Support calc() for scroll-snap

    Length values in scroll-snap don’t support calc().

    The Firefox and Safari implementations of this property both support calc().

    For example, this works in Firefox/Safari:

    -webkit-scroll-snap-points-y: repeat(calc(100vh - 100px));
    scroll-snap-points-y: repeat(calc(100vh - 100px));

    But this doesn't work in Internet Explorer or Edge:

    -ms-scroll-snap-points-y: snapInterval(0%, calc(100vh - 100px));

    27 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  CSS  ·  Flag idea as inappropriate…  ·  Admin →
  8. Update CSS Scroll Snap Points

    Now that both Firefox 39+ and Safari 9 supports it in addition to being in development in Chrome, updating the Scroll Snap Points implementation to match the current spec is crucial. The current implementation from the IE 10 days is outdated and incompatible with the changes made since then.

    Why hasn't there been any talk regarding this, and why hasn't it been done already?

    Spec: https://drafts.csswg.org/css-snappoints/

    77 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    on the backlog  ·  1 comment  ·  CSS  ·  Flag idea as inappropriate…  ·  Admin →
  9. Fix display: table* in respect to content overflow

    Currently the CSS table property when used in IE does not render sub elements of table-row and table-cell types correctly. Parent container sizes are not respected and content extends the table element regardless of overflow attribute.

    http://jsfiddle.net/jrbu4yc8/1/
    dragging/resizing the bottom left (yellow) element causes the entire document to expand regardless of overflow attribute. IE is the only browser to do this.

    16 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  CSS  ·  Flag idea as inappropriate…  ·  Admin →
  10. hanging-punctuation

    As defined by the spec, the `hanging-punctuation` property determines whether a punctuation mark, if one is present, hangs and may be placed outside the line box (or in the indent) at the start or at the end of a line of text.

    For most developers, CSS-tricks provides a sufficient explanation of its benefits that are often long-desired with critical textual content: https://css-tricks.com/almanac/properties/h/hanging-punctuation/

    42 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  CSS  ·  Flag idea as inappropriate…  ·  Admin →
  11. Implement ::selection according to Pseudo Elements Level 4

    ::selection has now been re-added to the spec: https://drafts.csswg.org/css-pseudo-4/#selectordef-selection

    You should considering starting to work on updating the implementating in Edge according to that spec. There are many bugs in the current implementation - you can't, for instance, write :root::selection or html::selection, and body::selection only applies to direct descendants, text nodes placed directly into <body> without wrapping. In the spec, it says: "Authors wanting multiple selections styles should use ‘:root::selection’ for their document-wide selection style, since this will allow clean overriding in descendants. (‘::selection’ alone would apply to every element in the tree, overriding the more specific styles of any…

    5 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 →
  12. Support data-uri for CSS cursor property

    Support data-uri for CSS cursor property. Especially useful as it eliminates loading gap when cursor is loading and is invisible to the user.

    Already supported in Chrome, Firefox, Opera and Safari

    42 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 →
  13. How do I include web pages background colors when printing

    Printing to the "Microsoft Print to PDF" Printer does not show background colors of table cells or DIV tags. How can I include these background colors in the "Print to PDF"?

    20 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 →
  14. css max and min

    Implement the CSS functions min() and max() as suggested https://www.w3.org/Style/CSS/Tracker/issues/203

    32 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  CSS  ·  Flag idea as inappropriate…  ·  Admin →
  15. Support `text-align: start` (& `end`) from CSS Text Module Level 3

    Add support for the `start` and `end` values of the `text-align` property, as specified in the CSS Text Module Level 3 spec ( http://dev.w3.org/csswg/css-text-3/#text-align-property ).
    These are very useful when writing stylesheets that take RTL (right-to-left) languages into account for page layouts.
    The other major desktop browsers already support them: https://developer.mozilla.org/en-US/docs/Web/CSS/text-align#Browser_compatibility

    73 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  CSS  ·  Flag idea as inappropriate…  ·  Admin →
  16. Support calc() in Flexbox rules

    Please just axe IE and don't rebrand with the Spartan project. You're literally the worst browser in every conceivable test http://html5test.com http://css3test.com and yet you make fun of people who critique you instead of dumping resources into fixing your garbage browser. https://www.youtube.com/watch?v=lD9FAOPBiDk

    So happy Chrome is bashing you nowadays. You deserve it.

    155 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  CSS  ·  Flag idea as inappropriate…  ·  Admin →
  17. 4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  CSS  ·  Flag idea as inappropriate…  ·  Admin →
  18. @document (css conditional rule)

    The @document rule has long been implemented in Firefox, but the W3C deferred further discussions about @document to CSS4, thus not carving anything out in stone - yet.

    Please make a push for getting the @document rule recognized and implmented in Edge, or something that works a similar way.

    Thank you!

    8 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  CSS  ·  Flag idea as inappropriate…  ·  Admin →
  19. :scrolling psuedoclass

    Currently, JS has to be used to apply styles to a scrolled container. It would be fantastic to have a psuedoclass like :scrolling or :overflowing to apply specific styling, like correcting for the space taken up by a scrollbar or perhaps applying a fixer header automatically.

    12 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  CSS  ·  Flag idea as inappropriate…  ·  Admin →
  20. Unprefix and support all @viewport properties

    CSS Device Adaption (http://dev.w3.org/csswg/css-device-adapt) is partially supported through the @-ms-viewport rule, however the width and height property are the only ones supported. It would be nice if the zoom and orientation properties were supported, too (in addition to the rest of the spec), so that we'd get a real replacement for the non-standard viewport <meta> tag.

    39 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  CSS  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base