Safari is the new IE6, stop supporting it and let it die. It will not get any better anyway. If most of your users are on iOS, then make an app for them, it's what Apple also want you to do...
Not sure what old wives tales you have heard, but actually Safari was the first browser to 100% support ES6.
And compared to Chrome, it uses 1/3 less battery...
- Apple didn't attend EdgeConf 2015
- https://webkit.org/blog/ was not updated often enough
- Safari 9 had a seriously buggy IndexedDB (fixed in Safari 10)
I'm not the only one who think Safari is a joke compared to the competition. While IE6 was much much worse than what Safari is today, I feel like history is repeating itself again. And ES6 support is irrelevant when the main goal is to make sure websites renders and behave correctly, which is more painful for Safari than the other browsers.
I still have flexbox issues on Safari https://bugs.webkit.org/show_bug.cgi?id=136041
How does that opinion survive reality, e.g. Safari being the first browser to reach 100% ES6 compliance?
>I still have flexbox issues on Safari https://bugs.webkit.org/show_bug.cgi?id=136041*
So? All browsers still have Flexbox issues. Here are Chrome's:
https://bugs.chromium.org/p/chromium/issues/list?can=2&q=com...
Notably Fetch API and WebRTC for my use-cases.
Hopefully they'll figure it out eventually!
I still use Chrome for development, though.
Safari, is not as bad as IE6 was and anyway no professional front-end developer would make a website that is not working properly on iOS Safari, so it's kinda obvious it will stay supported for a long, long time.
So I would consider what the OP is doing with the CSS, something that might also work on Safari, but with some polyfills.
I can only assume you never went through the pain that IE6 delivered... It has been some years now but I still get nightmares about it. It literally made me question at one time if I didn't made the wrong choice to focus on web development.
Apple may be dragging its feet when adapting new api stuff, but the situation is by no means comparable as what the situation was with IE6. Not by a million miles.
It's just my anecdotal view, but I believe that Chrome might be better for developers, but websites are made for the users, not the developers, and Safari is far superior on that front.
Chrome/Google has terrible/no support of many browser layout & interaction features, such as CSS Regions & scroll snap points.
Also, Safari is just a much better browser than Chrome. We need to make sure people stop using Chrome and move to the default browser in their environment - Safari & Edge.
If you support the default browser, then you're going to be fine.
Hi, I'm Linux.
( By the way lynx is perfect to pierce through a lot of paywalls. )
The alternatives are Opera and Firefox. Everything else is like coding while wearing mittens.
It gets tedious switching the default browser setting over so I tend to just use Chrome for everything.