- I don't own an iOS device, nor OSX - I feel like there is more browsers to tests
- Hardware access on mobile devices. Like Audio and Bluetooth Devices. Share Api and Push Notifications - Mobile browsers feature parity - different loading order between browsers - Assets loading and loading events implementation - Interpretation of cache control - It is fairly rare that I see browser compatibility issues. - I don't feel that browser compatibility is an issue anymore - Its fine! - Having to support old legacy browsers, such as Android 4.4 or IE 11 - Support for old browser (IE 11 most of the time) - Old browsers, e.g. Internet explorer and older versions of Safari. - interaction with built-in os features - lack of business clarity about who we support - need of third party libraries - Inconsistent performance. - a lot of memory consumption - Different performance bottlenecks across different rendering engines. e.g clip-path jank in chrome. 2D canvas context compositing performance differences - Trying to accurately measure performance across browsers when the APIs for getting RUM data are so different. - Polyfilling or avoiding modern JavaScript features in browsers that don't support
Other
Network
8
None
None
55
Old browsers
Old browsers
103
Other
Other
69
Other
Performance
36
Other
Polyfills
36
Made with FlippingBook - professional solution for displaying marketing and sales documents online