[Benjamin_Dobell]

It's really not just "trendy". Safari is the bane of my existence. On Big Sur, our WebGL app was occassionally sporadically rendering floating objects and black primitives into infinity on our CEOs laptop.

On the plus side, our competitor's product didn't work at all. So I guess it's not all bad.

In this case, Catalina had worked fine, and upgrading to Monterey fixed the issue. So props to Apple for fixing the problem. However, at the same time, our app worked flawlessly in both Firefox and Chrome running on the same hardware. Granted, it's not as simple as pointing the finger at Safari. The issue was a combination of Safari's behaviour paired with less than perfect graphics drivers.

Although, this is just one example. Mobile Safari not supporting full screen APIs on iPhone, but supporting them on iPad is just, well, weird. Is that a conscious effort to cripple the web on iPhone, or could they just not figure out the UX?

[merrywhether]

I actually like that they do this and let me use the UI I know and that will definitely work. 99% your video playback UX is not as good and you mostly want to take over full-screen so you can prevent the user from doing things (you may fall in the 1%, but I’m generalizing so apologies if you’re one of the few exceptions). It’s annoying on the iPad when sites build half-cocked full-screen UIs with buggy custom controls.

[Benjamin_Dobell]

As mentioned, our app is WebGL i.e. interactive real-time rendering, not at all video playback.

That said, I agree with you on custom video UIs being horrid.

[merrywhether]

Oh neat, and sorry for missing that. I can totally see why you might have valid reasons for that.

[stjohnswarts]

I guarantee it's not the latter given Apple's almost infinite resources.