4 ms·
And these are "total nonsense" for you? - SVG background issue from 2016. Tested on my Safari Tech Preview 113 (Sep 2020), can't replicate. - Clicking issue.
by HatchedLake721 5y ago
And these are "total nonsense" for you?
- SVG background issue from 2016. Tested on my Safari Tech Preview 113 (Sep 2020), can't replicate.
- Clicking issue. This is related to mouse event bubbling on iOS only (will affect both Safari and Chrome since they both use the same WebView). It's theorised that Apple set a specific set of rules when mouse events (on touch devices) will bubble up for performance/usability. Or it's just a bug.
- A rendering issue from 2012. It's explained in your link this is related to pre iOS 7 era performance improvement by WebKit to only redraw those parts of an image that have changed. Sounds like a very reasonable thing to do, taking into account how Apple heavily pushed performance and battery savings on mobile/laptop devices a decade ago.
- Round Corners. Tested on my Safari Tech Preview 113 (Sep 2020), can't replicate.
I don't see how any of these are anywhere close to being "total nonsense", feels like you're being biased and just exaggerating on purpose to bash Safari.
Chrome force logging in you when you use Gmail to hijack your privacy and link your browser history to an account sounds more "nonsense" than Apple focusing on performance/battery on mobile devices a decade ago that created a regression/new bug that requires 1 line to solve. https://news.ycombinator.com/item?id=17942252 https://news.ycombinator.com/item?id=17942252
I primarily use Safari for privacy/battery/performance reasons, and on my web app of 2 years with tons of styling I have 5 lines of scss code with "// safari" comment to make some elements render the same as Chrome.
Never in my career writing a single digit line of additional css made me think "oh my god this is total nonsense". Everyone has to accept there will be differences from one browser engine to another, and from my personal experience, these are minimal and nowhere near IE6 back in the days.
- saagarjha 5y agoWhy are you running a Safari Technology Preview from last year?
- HatchedLake721 5y agoI'm still on macOS Catalina. To upgrade the Safari Technology Preview, it wants Big Sur first and I just haven't got to upgrading my dev laptop yet. Something to do this weekend then!
- bengale 5y agoOur web app has a single safari exception in the CSS and I'm pretty sure it's fixed in the latest version, just waiting for it to be more widely updated on peoples machines.
- realusername 5y agoYou are right, those bugs are very old but the desktop bugs mentionned are still replicable on Safari 13 at least, the iOS bug is at least replicable in iOS 13 and I have no reason to think it's fixed (yes you are right, this click bug has been there since 2012 at least, that's been 9 years now). > I primarily use Safari for privacy/battery/performance reasons, and on my web app of 2 years with tons of styling I have 5 lines of scss code with "// safari" comment to make some elements render the same as Chrome. You are within your own right to use Safari but you should not expect everything to work perfectly in return, treat it as "best effort" web browsing. On my case I have about a dozen lines of CSS and same in JS for all the Safari quirks. All of those took time to investigate and fix (especially with their awful debugger...), maybe there's more Safari bugs, I just cannot guarantee everything works.