luceos I have no doubts you're right about Safari being the new IE. I'm not sure what can be done though since due to the iPhone popularity it's one of the most popular mobile browsers (I wouldn't be surprised if it's the most used mobile browser, at least with my forum that's what the stats say). I've even reported Flarum issues to Apple, asking them to log in to my forum and see some problems 🤣 Of course, they probably won't ever do that, but at least it's some annoyance to them and if many people start reporting issues to them (not just with Flarum), they may change something. As a matter of fact, I'm a regular reporter of various issues to Apple as a member of their Beta program and I've had one or two instances when I was contacted directly by engineers that ultimately solved the issues, so it's not entirely hopeless after all.
But what I wanted to say (and I intentionally left it as a second paragraph because it starts with "but") is that even though Safari is an offender and doesn't follow standards, sometimes devs have to make sacrifices when it's about one of the most popular browsers. As a developer myself I know the frustration of having to cope with non-standard API-s, broken contracts, etc., however I've been faced with angry customers that don't care whose fault it is, they just want it nice and working and so, we have to swallow it and just make it working... Not saying that's what you have to do, but just saying you may want to double-check on mobile Safari from time to time, just to be aware of what complaints you may get sooner or later from many iPhone users.
