instability places an unfair maintenance burden on the developers, wasting time and money. - Chrome and Firefox are starting to diverge, with chrome adding features before they're fully standardized. As the dominant browser, some pages are being written to only work in chrome now. - Google releasing features in Chrome with no developer or standards committee backing. And later deprecating them without any alternatives. - Inconsistent support for standards with some having been around for ages like dialog Chromes developing attitude reminiscent of the bad old days of IE setting own standards. - CSS. There is just always issues with CSS - Browsers that have behaviours different from the standard, or bugs, specially in CSS (Safari, I'm looking at you). - Firefox doesn't handle column layout properly, and will only draw it inside a flex container on page refresh. - MS Edge (non-Chrome version) - Still having to support MS IE 11 and non-Chromium MS Edge - From IE11 to Edge 15. - On one app I have differences between ff and WebKit on mouse event handling and have to support a different design on Firefox because blurs don't work as expected on ff - input specific javascript events like mousewheel - https://stackoverflow.com/questions/59751 598/inputevent-datatransfer-is-always-null
Chrome
Chrome
86
Layout & styling
CSS
158
Edge
Edge
42
Other
Events
16
Other
Extensions
7
- Web Extension API differences between
Made with FlippingBook - professional solution for displaying marketing and sales documents online