OngoingWork Browser compatibility has been an issue for the entire history of the World Wide Web, and we do not expect to be able to fix it entirely. Nevertheless, the purpose of this report is to highlight specific issues which are concrete enough for browser vendors to prioritize. In conversation with the engineering teams, these are the efforts we know of at the time of publishing.
Improving Chromium's browser compatibility in 2020 outlines various efforts happening in the Chromium project, some of which is repeated below.
CSS Flexbox & Grid CSS Flexbox and CSS Grid emerged as two of the features causing the most issues in this research. As described in the blog post , improvements to both are in progress in Chromium, and notably flex-gap and fieldset+flex support shipped in Chrome 84 in July. In WebKit, Igalia have been contributing a lot of Flexbox fixes , specifically around height and aspect ratio. Microsoft Edge The issues identified with Microsoft Edge in this survey, which was conducted in February/March 2020, were specifically for EdgeHTML in Microsoft Edge Legacy. It will reach end of life on March 9, 2021 , and as of June 2020, the new Chromium-based Edge is rolling out with Windows updates to Windows 10 (see blog post ) as well as Windows 7 and 8.1 , and is available on other platforms like macOS and Linux. Therefore, we expect a natural phasing out of these particular issues for developers. Browser Compatibility Data To help developers better understand which features will work where, accurate and up-to-date compat data is key. Such data can also help browser vendors get an overview of the state of browser compatibility and what needs to be addressed to offer the best possible platform for developers.
Made with FlippingBook - professional solution for displaying marketing and sales documents online