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. 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 →
  2. Update CSS Regions

    Update the IE implementation of Regions to match the current spec and interoperate with the Safari implementation

    91 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 →
  3. Update word-wrap to overflow-wrap

    overflow-wrap is the new name for word-wrap, and should be implemented to adjust to the standards.

    55 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 →
  4. font-family should be stored as array of strings, not a string that requires parsing (escaped quotes)

    Previously IE and Firefox use to have similar behavior but now since Firefox aligned itself with Chrome (Blink) behavior, I think IE should change its behavior and make all browsers consistent.

    Test URL: https://bugzilla.mozilla.org/attachment.cgi?id=172901

    Bug URL: https://bugzilla.mozilla.org/show_bug.cgi?id=280443

    Regards

    5 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 →
  5. 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 →
1 2 3 4 5 7 Next →
  • Don't see your idea?

Feedback and Knowledge Base