Microsoft is very open about developing its web browser. Currently, the team dedicated to its development is significantly larger than it was in the previous few years. By removing the old code for compatibility with Stone Age websites and leaving it to its fate in IE, the implementation of new standards in the modern browser is significantly faster than it was in the past. All that remains is to tell Microsoft what it should focus on in its development.
Feedback and bug reports
Feedback Hub
One channel for sending feedback about the quality of the browser is available directly in Windows. It is not only designed for Edge, but serves as a hub for gathering suggestions to improve the operating system and related services.
issues.MicrosoftEdge.com
In addition, there is a bug reporting portal that allows you to provide more detailed information. It is focused more on frontend developers. The experienced ones should know the error tracking systems of all major browser cores, so here is the whole list:
- EdgeHTML (Microsoft Edge): issues.MicrosoftEdge.com
- Gecko (Mozilla Firefox): bugzilla.mozilla.org
- WebKit: bugs.webkit.org
- Chromium: Crbug.com
Twitter hashtag #EdgeBug
Twitter can also be used to report bugs briefly and quickly. Just use the hashtag EdgeBug and the Tweet will be written to the internal bug tracking system (Visual Studio Team Services).
Functional requirements
uservoice.MicrosoftEdge.com
A common problem for developers is not so much the fact that something works badly, but that something doesn't work at all. That’s why there is Microsoft Edge Developer Feedback, which gives developers the opportunity to vote for new features that they would like to see in the next version of the browser. Individual voices then play a role in deciding what browser developers focus on. The total number of votes does not play such an important role as their even distribution over time.
status.MicrosoftEdge.com
Similar features are offered by Platform Status, with the only difference being that the list of standards is maintained by Microsoft itself. Therefore, you will also learn from the page what is being worked on, what is already available in the preview, which browsers support what, or the implementation of what is being considered.
Statistics
data.MicrosoftEdge.com
There are currently two interesting statistics on the Platform Data page. CSS Usage shows on what percentage of pages individual CSS properties occur. API Catalog then visualizes the results of the analysis of the implementation of individual standards in different browsers.
Testing
EdgeHTML is available only for Windows. However, fans of other operating systems can use virtual machines that Microsoft offers to test the compatibility of web computers with IE8 – IE11 and MSEdge for free.
developer.microsoft.com/en-us/microsoft-edge/tools/vms
Does it actually make sense?
Many web developers wonder if it makes sense for Windows to include a web browser as an integral part of it. However, Microsoft and Google are of the opinion that no private company should ever fully control the Internet. By controlling the compiler, operating system, and browser, Microsoft can continually reduce the number of 0-day vulnerabilities and keep improving performance. Microsoft is also able to come up with innovations that it would otherwise not be able to implement and would remain on paper. Windows 8 enabled application development in a combination of HTML/CSS/ECMAScript in addition to the traditional C#/XAML assembly. Because HTML has historically been used to render text documents rather than position controls, Microsoft decided to port the Grid from XAML to CSS. Thanks to the cooperation of web browser development teams, the CSS Grid specification was eventually created.