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. Create an updated CSS Regions capability

    Modern web layout and design is getting closer to print media. Using the spirt of CSS Regions, be able to set up the capability of flowing into empty grid track cells and utilize generation of grid tracks.

    93 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  CSS  ·  Flag idea as inappropriate…  ·  Admin →
  2. object-fit and object-position for all media elements

    Object-fit and object-position is defined for all visual media, not only for images, but also for video or canvas elements.

    1,247 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    22 comments  ·  CSS  ·  Flag idea as inappropriate…  ·  Admin →
  3. break-word

    Support `word-break: break-word` please.

    121 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  CSS  ·  Flag idea as inappropriate…  ·  Admin →
  4. Bring `gap` property to flexbox

    As outlined in the linked issue, having the ability to use grid-gap on flexbox (which is soon to be renamed just "gap" by the CSS Working Group because "grid-gap" doesn't make sense when used on flexbox) solves a major pain point that developers are facing.

    See the issue for more details:
    https://github.com/w3c/csswg-drafts/issues/592

    270 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  CSS  ·  Flag idea as inappropriate…  ·  Admin →
  5. Fixed header on tables with scrolling tbody

    Please support existing Chrome functionality that supports scrolling tbody and fixed header in responsive tables! Many posts on Stack Overflow trying to achieve this cross-browser capability, already available in Chrome.

    9 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  CSS  ·  Flag idea as inappropriate…  ·  Admin →
  6. 39 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  CSS  ·  Flag idea as inappropriate…  ·  Admin →
  7. 1 vote
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  CSS  ·  Flag idea as inappropriate…  ·  Admin →
  8. 27 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  CSS  ·  Flag idea as inappropriate…  ·  Admin →
  9. 45 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  CSS  ·  Flag idea as inappropriate…  ·  Admin →
  10. 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…

    124 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  CSS  ·  Flag idea as inappropriate…  ·  Admin →
  11. Implement CSS `display: flow-root` (modern clearfix)

    `display: flow-root` is a modern way to force a block to be a formatting context that floated elements are contained in (aka clearfix).

    From the spec [1]:

    > The element generates a block container box, and lays out its contents using flow layout. It always establishes a new block formatting context for its contents.

    Tab Atkins and Elika Etemad (fantasai) from CSSWG consider the feature stable enough to be implemented [2].

    [1] https://drafts.csswg.org/css-display-3/#valdef-display-flow-root
    [2] https://discourse.wicg.io/t/1835/6

    2,007 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    27 comments  ·  CSS  ·  Flag idea as inappropriate…  ·  Admin →
  12. Support Media Queries level 4 syntax improvements

    CSS Media Quries Level 4 bring in a bunch of syntactic improvements. They make media queries much more readable and maintainable.

    https://drafts.csswg.org/mediaqueries-4/#mq-syntax

    Here's an example:

    Before:

    @media (min-width: 20em), not all and (min-height: 40em) {
    @media not all and (pointer: none) {

    }
    }

    After:

    @media ((width >= 20em) or (height < 40em)) and (pointer) {

    }

    108 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  CSS  ·  Flag idea as inappropriate…  ·  Admin →
  13. Isolation

    Used to declaratively create a new stacking context.

    https://drafts.fxtf.org/compositing-1/#isolation

    12 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  CSS  ·  Flag idea as inappropriate…  ·  Admin →
  14. 304 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    9 comments  ·  CSS  ·  Flag idea as inappropriate…  ·  Admin →
  15. 113 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  CSS  ·  Flag idea as inappropriate…  ·  Admin →
  16. #rrggbbaa and #rgba color notation support

    Couldn't find this anywhere here, so I'll post this feature request.

    I'm asking for support of the following notations:

    background-color: #12345678;

    and

    background-color: #1234;

    Spec: https://drafts.csswg.org/css-color/#hex-notation

    321 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  CSS  ·  Flag idea as inappropriate…  ·  Admin →
  17. mak a 3d printer thet cen mak food for me an my famili

    we dont hav mani food in our villeg,so we ned a food supplie

    7 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  CSS  ·  Flag idea as inappropriate…  ·  Admin →
  18. Implement the display: contents

    When using layout modes like flexbox and grid, there is a conflict between the desire to keep the DOM tree relatively flat, to avoid complex, unperformant, highly-nested layouts, and grouping elements in a way that makes sense semantically and allows easy manipulation via data-binding frameworks like Angular.

    This conflict can be solved by supporting the "display: contents" box-generation mode from CSS Display Module Level 3. This allows elements to be configured to generate no box of their own, only those of their children. In this way, complex, nested DOM structures can generate much simpler box trees.

    3,976 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    217 comments  ·  CSS  ·  Flag idea as inappropriate…  ·  Admin →
  19. Implement caret-color support

    "caret-color" has just been implemented on Chromium and Firefox. It'd be really nice if Edge can support it too.

    The spec is CR: https://www.w3.org/TR/css-ui-3/#caret-color

    And there are already 21 tests on the W3C csswg-test repo: http://test.csswg.org/shepherd/search/testcase/spec/css-ui-3/section/6.2.1/

    107 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  CSS  ·  Flag idea as inappropriate…  ·  Admin →
  20. Implement :focus-within from Selectors 4

    Tons of UIs include elements that are not visible unless the user interacts with their parent or ancestor. Think popup menus, delete or edit buttons, floating formatting toolbars, copy buttons, editing popups and so on. The list is endless. This is a good way to reduce visual clutter.
    However, this is often done in an inaccessible way, just by using :hover, because making it accessible requires JS, since :focus does not apply to ancestors. However, 1 in 2 people writing HTML/CSS are not comfortable with JavaScript so keyboard accessibility (and usability, as many of us are keyboard users by choice)…

    2,097 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    27 comments  ·  CSS  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5 6 7
  • Don't see your idea?

Microsoft Edge Developer

Feedback and Knowledge Base