MDN-Browser-Compatibility-Report-2020

them. - Too many polyfills is confusing - Supporting old browsers with tons of polyfills - When we have to differentiate every css prop for specific browser - the css vendors prefix are a pain. the same js prefixes are more easy to handle as they can be dynamically "renamed" - Vendor prefixed features and support of new features - Lack of PWA support, especially on iOS - Full support of the PWA set of technologies between all major browsers. - Cutting edge features that try to implement native mobile app functionality move too slow and are unevenly supported - Biggest issue is the small layout differences between render engines. - Unexpected behaviors with positioning. - When I hear from a client that what they're seeing is not what I'm seeing. - iOS safari is slow to adopt most features, especially PWA features - webp image format support for safari - Bugs and missing features in WebKit. - How scroll bars affect layout - Inability to style browser scrollbars - Scrollbar bugs and inconsistent behavior between browsers regarding scrollbars. Layout calculations, async issues. It's not just that these are incredibly annoying to determine and debug, it's that they differ per browser and finally it feels like nobody else on the internet talks about these issues even though I'm sure everyone has them.

Other

Prefixes

21

PWAs

PWAs

43

Layout & styling

Rendering

69

Safari

Safari

229

Layout & styling

Scrollbars

10

Other

Scrolling

14

- Controlling scroll behavior: when does a

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