![]() This new engine was a break from the past: including a new user-agent string, ending support for legacy document modes and other Internet Explorer-specific technologies like ActiveX, and aiming instead to focus on the “interoperable intersection” of APIs supported by modern browsers and sites across the web. ![]() Later that year, we took the first concrete steps when we shipped the first preview of our new evergreen engine (EdgeHTML). In 2014, we articulated our ambitions for what would become the new engine for Microsoft Edge when we shared our web platform priorities for Windows 10: getting users current, improving security, and delivering on both modern web interoperability and reliable backwards compatibility. Today, we’d like to reflect on our progress in 2015 towards delivering a great rendering engine for web developers in Microsoft Edge, and share some of the metrics we track to evaluate how we’re doing against that goal. Just five months later, there are over 200 million devices with browsers and apps powered by EdgeHTML across PCs, tablets, phones, and Xbox One. Just a couple of weeks before the 20 th anniversary of Internet Explorer 1.0, we broke from the past with our brand new browser for Windows 10, Microsoft Edge. 2015 was a historic year for the web on Windows.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |