4 ms·
why checking for specific browser rather than using feature detection to properly handle different browser capabilities? ( Good docs at https://developer.mozil
by amatecha 3y ago
why checking for specific browser rather than using feature detection to properly handle different browser capabilities? ( Good docs at https://developer.mozilla.org/en-US/docs/Learn/Tools_and_testing/Cross_browser_testing/Feature_detection https://developer.mozilla.org/en-US/docs/Learn/Tools_and_tes... )
- mattnewton 3y agoFor safari, I used to run into a lot of graphical bugs, (especially when pushing things into layers on the gpu with transforms). The second big category would be things that are performant on low end android phones with chrome are not performant on older iPhones and vice versa.
- no_way 3y agoSemi related, I was suprised just how many bugs Safari has with animation timing while using Web Animation API. You can't possibly feature detect that, Motion one lib even disables GPU acceleration for them in Safari. In that case parsing user agent is the only option. https://motion.dev/guides/waapi-improvements#webkit-bugfixes https://motion.dev/guides/waapi-improvements#webkit-bugfixes