Microsoft to share Edge platform data from API Catalog and Global CSS usage

Reading time icon 2 min. read

Readers help support Windows Report. We may get a commission if you buy through our links. Tooltip Icon

Read our disclosure page to find out how can you help Windows Report sustain the editorial team Read more

Leveraging some pretty significant announcements revealed during Build 2016, Microsoft is continuing to ring the bell of openness and transparency. During the company’s Edge Summit, details about Microsoft’s new web browser have been shared, including stats on its usage as well as potential features coming being discussed by the engineers currently working on the project.

Among the announcements during the Edge Summit was the mention of Microsoft’s plan to share Edge platform da gathered from its API Catalog and Global CSS usage. Perhaps, insignificant to the common everyday web browser on Windows 10, the new information could be invaluable to developers leveraging new interoperable technologies across browsing experiences.

In particular, developers can look forward to:

API Usage

  • We use data gathered from various large-scale crawlers to see which front-end APIs are actually used on real sites across the web. This section not only allows you to see which APIs are the most used but also which sites are using them and how they’re being used.

API Catalog

  • Coding to Web standards is tricky—HTML, CSS, and JavaScript consist of more than 300 W3C specifications from over 400 member organizations. No browser implements every standard, and each browser implements a different subset of specifications in addition to proprietary APIs. This tool compares major browsers’ API sets alongside standards specifications so that you can target the “interoperable intersection” of web technologies.

Microsoft has taken a huge risk by breaking development between its tried and true Internet Explorer for its more modern web standard compliant Edge browser. However, in doing so, the company has set its development on the right path of including interoperable, developer requested and standard compliant features in a much timely manner in the future.