7 ms·
Mobile Safari does hold the Web back. Examples are easy to find: Safari doesn't support the standard unprefixed fullscreen API, while Firefox and Chrome have f
by roca 6y ago
Mobile Safari does hold the Web back. Examples are easy to find:
Safari doesn't support the standard unprefixed fullscreen API, while Firefox and Chrome have for years, so Web developers have to write a bunch of compatibility crap or accept fullscreen not working on iOS.
Firefox and Chrome have supported WebGL2 for years, iOS Safari still doesn't.
- deleted 6y ago[deleted]
- ascagnel_ 6y ago> Safari doesn't support the standard unprefixed fullscreen API, while Firefox and Chrome have for years, so Web developers have to write a bunch of compatibility crap or accept fullscreen not working on iOS. Having used an iPad for general web browsing for a while, the worst change they made was allowing web apps write their own fullscreen interfaces. I can't think of any video website where they've done a better job at basic video player controls than what the OS does natively.
- roca 6y agoFullscreen isn't just for video though. It's very commonly used for games. I also wrote fullscreen support for "DOM videos" (e.g. https://pernos.co/about/overview/ https://pernos.co/about/overview/) using the fullscreen API. The latter doesn't even support Webkit because the compatibility work was just too hard.