`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

Put the Favourites links back into the users' favourites folder on the desktop. The current location of Edge favourites' links is utterly ridiculous - the pathway is about a page long, and clearly intended to prevent users from directly managing their bookmark links the same way we could with IE. This is ****, and if MS had any sort of interest in their clients and user base, they wouldn't make such stupid, alienating, non-consultative decisions.
Fix this now, before we all choose Firefox instead !!!!!!

Put back the toolbars and users' ability to customise them. You've really buggered up your own product here. What idiot approved development of a product that doesn't have at least the same functionality as the one it replaced? Edge may run faster, but your users have to waste their own time doing simple **** like printing, which is now no longer a simple click on a single button. Edge doesn't even preselect the buttons it does have. MS, stop screwing your user base and forcing us into other user friendlier apps.

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) {
…
}

Used to declaratively create a new stacking context.

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

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.

I could justify this all I want but in short: websites still use flash and some will never be updated. Some are for education as well. Just give us an option to enable the button/checkbox in the advanced settings.

Meaning you dont have to click on the adres bar anymore after opening a new tab.

The old version of this tool showed me the actual payload string but now shows the key/val pairs broken down and sorted alphabetically. This isn't useful for me any more. Please include an option to show the ACTUAL payload string as is built and sent.

The WebXR Device API is the future of WebVR/WebAR and is a must have for Mixed Reality devices and all other platforms. Google has started implementing this in the canary version. Please don't get behind.

Links:
- https://immersive-web.github.io/webxr/
- https://github.com/immersive-web/webxr

https://github.com/whatwg/fetch/pull/733

I would fix -it myself if I had the menu bar and of course permission

Remembering where I left is like a bookmark we leave in the last read page.

New css 'speak' properties and more: https://drafts.csswg.org/css-speech/

An API that returns a map which translates from `KeyboardEvent.code` values into a strings that can be shown to the user to identify each key.

This is not possible with existing web platform APIs because the value that should be shown to the user depends on the keyboard layouts that the user has installed and active.

WICG incubation spec: https://wicg.github.io/keyboard-map/

Note: there is some overlap between this and a previous feature request https://wpdev.uservoice.com/forums/257854-microsoft-edge-developer/suggestions/6508637-uievents-keyboard-query-apis

The previous request was based on an old proposal that is no longer being pursued in the standards bodies.

Don't take the focus from a text box or user entry when pop-ups show up. It make the user experience very annoying. It should leave the focus on the text box the user is using and/or actively typing in so that they can finish their standard task.

Edge on Android is freakin awesome, but a little more refinement will make edge even more enjoyable to use.

1. Move the home button to the navigation bar instead of having it at the to near the address bar.
2. Make the hub more easier to reach, It is up top which make it hard to reach on big phones.
3. On the tab page, bring the Tab selection header to the bottom.

Lookbehind assertions are now part of the ECMAScript specification. Google's V8 has had an implementation of it for a while now.

See: https://github.com/tc39/proposal-regexp-lookbehind