MDN-Browser-Compatibility-Report-2020

General

General

142

- Lack of consistency between browsers - browser differences that can't be feature-detected - differences in un-spec-ed behavior - Lack of browser support for features, e.g. ResizeObserver, createImageBitmap, WebGL2, WebAssembly worker-based threads. - Different performance bottlenecks across different rendering engines. e.g clip-path jank in chrome. 2D canvas context compositing performance differences - Safari handling webgl differently than firefox/chrome. - Waiting for CSS specs to be fully available every where. Mainly css grid. - CSS Grid bugs and mobile viewport behaviour. - layout, e.g. css grid and css flex missing from older browsers - Having basic HTML5 features not supported in all web browsers. - using the latest HTML 5 attributes and modern API's - different implementations of same tag or element property with spacing/sizes in different browsers - Having to support Internet Explorer is my top pain point. Our customers are stuck on old software they cannot easily update. - IE 11, which is still the default internal browser for my organization. So it must be fully supported, meaning if we can't make something work at near 100% parity in IE, we can't do it. - Support for old browser (IE 11 most of the time)

Other

Graphics

5

Layout & styling

Grid

23

Other

HTML

12

Internet Explorer

Internet Explorer

348

Safari

iOS

27

- Safari, particularly the iOS version.

Made with FlippingBook - professional solution for displaying marketing and sales documents online