Microsoft Edge Web Summit 2016 Entries Available - Part 1
Immediately after the Build conference (we made a broadcast on Habré: day 1 and day 2 ), our colleagues held another conference in San Francisco, but more focused - about client web technologies and news in the Microsoft Edge browser.
Looking back: One year of Microsoft Edge
In the framework of the Microsoft Edge Web Summit 2016 conference, engineers from the Edge team shared their experience in developing a new browser, talking about new supported standards and future plans.
')
The conference also announced a number of tools that make the development of Microsoft Edge and the web platform more transparent to the community:
Clarice Chan talks about the experience of releasing a new browser and working with user requests for new features and investing in new ways to interact with the web.
Jacob Rossi talks about the team’s plans for 2016: from the upcoming releases to long-term investments and research into the future of the web platform.
Kiril Seksenov talks about the Edge engine inside the universal Windows platform (UWP) and the possibilities of using current code and web development skills to access the native Windows API capabilities.
David Weston shares his experience in working with holes in the browser and the team’s work on protecting the browser from attacks, including improvements such as MemGC, modular code integrity and AppContainer isolation.
Rob Trace talks about the work of the FIDO Alliance and W3C on user authentication and a new experimental feature in Microsoft Edge - .msCredential, implementing FIDO API based on Windows Hello.
Todd Reifsteck shares his experience using the Windows Performance Toolkit to analyze website performance.
Greg Whitworth explains how to use data when deciding where to invest development time, what new features to implement, what bugs to close first, and what improvements will give the greatest return.
Colleen Williams and Anton Molleda continue the topic of working with bugs (in the browser, websites, frameworks and third-party applications) and tell how their team interacts with developers and how you (yes!) Can help the team work it is better.
To be continued ...
Looking back: One year of Microsoft Edge
In the framework of the Microsoft Edge Web Summit 2016 conference, engineers from the Edge team shared their experience in developing a new browser, talking about new supported standards and future plans.
')
The conference also announced a number of tools that make the development of Microsoft Edge and the web platform more transparent to the community:
- Platform Issues is a new place to report bugs and learn about already known issues in EdgeHTML (see also the article “ Introducing the Microsoft Edge Platform Issue Tracker ”).
- Platform Data - API and telemetry catalog on the global use of CSS properties (see also the article " Introducing Global CSS Property Usage on Microsoft Edge Dev ").
- Updated Microsoft Edge virtual machines on OSX and Linux
Level up: Building on a brand-new browser
Clarice Chan talks about the experience of releasing a new browser and working with user requests for new features and investing in new ways to interact with the web.
What's next for EdgeHTML?
Jacob Rossi talks about the team’s plans for 2016: from the upcoming releases to long-term investments and research into the future of the web platform.
EdgeHTML and the Windows Universal App Platform
Kiril Seksenov talks about the Edge engine inside the universal Windows platform (UWP) and the possibilities of using current code and web development skills to access the native Windows API capabilities.
The Cutting Edge of Browser Security
David Weston shares his experience in working with holes in the browser and the team’s work on protecting the browser from attacks, including improvements such as MemGC, modular code integrity and AppContainer isolation.
Strong Authentication and the road to FIDO
Rob Trace talks about the work of the FIDO Alliance and W3C on user authentication and a new experimental feature in Microsoft Edge - .msCredential, implementing FIDO API based on Windows Hello.
Top-Down Performance Analysis with Windows Performance Toolkit
Todd Reifsteck shares his experience using the Windows Performance Toolkit to analyze website performance.
Using internet-scale data to guide product planning
Greg Whitworth explains how to use data when deciding where to invest development time, what new features to implement, what bugs to close first, and what improvements will give the greatest return.
How We Engage Your Ecosystem
Colleen Williams and Anton Molleda continue the topic of working with bugs (in the browser, websites, frameworks and third-party applications) and tell how their team interacts with developers and how you (yes!) Can help the team work it is better.
To be continued ...
Source: https://habr.com/ru/post/282023/
All Articles