Hacker News new | past | comments | ask | show | jobs | submit login

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_tes... )



For 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.


Semi 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




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: