Migrated from Edge Bug report: https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/21312153/
________________________________________________________

It would be nice if Edge DevTools could log a message for sites that are running on TLS 1.0 or 1.1.

As we get closer to disabling TLS 1.0 and 1.1, we should log a message to the console for sites that do not speak TLS 1.2 (or 1.3), and link to a useful resource, perhaps https://blogs.windows.com/msedgedev/2018/10/15/modernizing-tls-edge-ie11/, and better docs in the future as we have them.

We just landed a similar thing in Firefox Nightly, see https://bugzilla.mozilla.org/show_bug.cgi?id=1512505, the message we ended up with was: "This site uses a deprecated version of TLS that will be disabled in March 2020. Please upgrade to TLS 1.2 or 1.3."

I filed https://bugs.chromium.org/p/chromium/issues/detail?id=955645 for Chrome -- I'm not sure what the release schedule is for Edge on Chromium. If it will be stable by Oct 2019-ish (when browsers will start to disable TLS 1.0/1.1 in pre-release builds (maybe)), this is a WONTFIX. But if it's later than that, it's probably good to land this in current EdgeHTML Edge DevTools.

Provide a single web browser that can support legacy enterprise applications as well as modern web development practices and features.

Internet Explorer continues to be the most used browser even on Windows 10 PCs at the enterprise I work for. This is a problem when I reach for modern browser APIs and features since IE stopped advancing when Edge came on the scene. A comparison of IE 11, Edge 18 and Chrome 73 paints a picture: https://caniuse.com/#compare=ie+11,edge+18,chrome+73

I realize maintaining IE's backwards compatibility blotted it over the years but hey, it comes with Windows so it doesn't really matter. If the Edge team still wants a light weight, edgy, browser for mobile devices and the like good on you but please make advancements available to IE users in an intuitive way that doesn't require jumping between different browsers. Perhaps this could be accomplished similarly to the FF and Chrome sandbox extension that uses Edge behind the scenes. People don't care how things work, only that they work.

Hindsight:

In 2015 Internet Explorer was finally starting to act like a modern browser and then Edge appeared, and development of IE ceased, except to address security issues. At the time I was excited for Edge but I did not anticipate the impact it would have on IE or that IE would have such staying power in the enterprise.

The existence of "Open in Internet Explorer" is a terrible user experience and demonstrates that there is something wrong, both from a web developer's perspective and end-user's.

The similarity of the Edge and IE logo is a problem for regular people who don't care about technology, they care about getting their jobs done. Most people think they are getting Microsoft IE re-branded when they open Edge and just expect things to work, but certain enterprise applications don't work because it only works in IE. Why billion dollar companies cannot update their software to support modern practices is beyond me but this is the reality we live in, and the last 4 years demonstrate that no effort on Microsoft's part can compel those companies to change.

* I originally named this "Merge Internet Explorer and Edge into the same product" but I didn't think it would catch on.

Please make Google Translate Extension work with Edge Chromium
Make Google and Bing Translate have right-click context menu for ease of use
Reduce the spacing in Extension icons that are next to the address bar - too big

Make extensions that are hidden in the menu not to come back to the tool bar, after you have disabled a different extension - what stays in the menu, stays there and doesn't come up unless you choose to bring it up

Please consider replacing the word Favourites with Bookmarks

Please change the Loading Icon animation/GIF that appears on top of the tab - it leaves you with a feeling of slowness as the page loads - make the circular movements move faster (Give a sense of fast speed) or change them to two dots that have a linear motion as they appear on firefox or remove the connected circular moving dots - let it be a continous circular line like that of Chrome - please, please, please - give this your consideration - don't give users any appearance of slowness

There's a lag on YouTube, at times, when you open a YouTube video page, video loads up to about even 30 seconds, but the video doesn't play at all, unless you refresh

When you open two YouTube pages, it loads slowly or lags because of the second page - if you switch to the second page, you find that the page was trying to load, when you close it, the first page starts playing without a lag - make it possible to open two or more YouTube pages without the lags even when your internet connections is fast - I use Iridium chrome extension and Video Speed Controller, so am not sure if its the extension or it's Edge browser

Microsoft, if you love your users and want more people to use edge and adopt it - CHANGE THE ICON FOR EDGE BROWSER - it should not look or have any resemblance to the old Internet Explorer - IE is a big turn off, it feels like you're using an old resurrected browser that has had a bad reputation - Give it some sense of new browser and you will see more people adopting it.

Trapping focus in modal dialogs or preventing focus in background layers in modern web applications is extremely difficult and error-prone. Developers either have to walk the DOM and disable every focusable control with tabindex="-1" and `aria-hidden="true"` on a parent element, or do some tricky JavaScript to maintain focus inside of an element. Many developers get this wrong or they don't do it at all, creating horribly inaccessible experiences for keyboard and screen reader users.

The inert attribute currently being explored in the WICG solves this problem by providing a mechanism to disable entire subtrees in HTML. By setting `inert` on an HTML element, it renders every interactive control non-focusable and removes it from the accessibility tree.

https://github.com/WICG/inert

Inert means no more walking of the DOM to set and restore tabindex, and forgetting to set `aria-hidden="true"` on a parent element (it happens all the time). The inverse also commonly occurs–developers set `aria-hidden="true"` on a parent element, and forget to modify tabindex on links and buttons, causing "ghost controls" with no accessibility information. Like I said, it's extremely error-prone. We need `inert` to make these scenarios much easier. It's a breeze in comparison! Set it on a sibling element to the one that remains visible, and you can handle focusability and AT access in one go.