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