3 ms·

iOS Safari (for iPhone) still does not support the Fullscreen API. Works fine on iPad, but not iPhone. Why? https://developer.mozilla.org/en-US/docs/Web/API/Fu

iOS Safari (for iPhone) still does not support the Fullscreen API. Works fine on iPad, but not iPhone. Why? https://developer.mozilla.org/en-US/docs/Web/API/Fullscreen_API#document.fullscreenelement https://developer.mozilla.org/en-US/docs/Web/API/Fullscreen_... And some weird CSS behavior that only exists in Safari right now: like :first-child selectors, limited flex-basis values, the gap property not working in a multi-column layout... It's mysterious discrepancies like this that drive me insane doing frontend for iOS. Apple can't spend a crumb of it's $2T+ getting their browser and dev tools up to par with even Firefox? Please

smoldesu 5y ago
> Apple can't spend a crumb of it's $2T+ getting their browser and dev tools up to par with even Firefox? Ugh, please. They've only got a mere 200 billion in liquid cash.
acdha 5y ago
Two things: that's not “a buggy mess” unless you think Firefox/Chrome magically turn into one if you use one of the APIs which Safari supports which they don't or have bugs with. Again, remember that I wasn't saying that there are no problems, only that they were exaggerating the magnitude and degree to which it's specific to Safari. Second, this is not only not “a buggy mess” but a conscious design decision and one which I generally agree with. Safari supports full-screen video, which is the primary reason why I want this, and the full-screen API is a notorious security risk on touchscreen devices even more than traditional computers because you don't have the equivalent of the escape key or the operating system UI giving you a way to tell that the “Please enter your password” dialog which just popped up was generated by the web page and not your OS. On iOS, Safari is already close to full screen anyway so the extra few pixels is less than what you'd need to account for in different screen heights between devices anyway.

smoldesu 5y ago

> Apple can't spend a crumb of it's $2T+ getting their browser and dev tools up to par with even Firefox? Ugh, please. They've only got a mere 200 billion in liquid cash.

acdha 5y ago

Two things: that's not “a buggy mess” unless you think Firefox/Chrome magically turn into one if you use one of the APIs which Safari supports which they don't or have bugs with. Again, remember that I wasn't saying that there are no problems, only that they were exaggerating the magnitude and degree to which it's specific to Safari. Second, this is not only not “a buggy mess” but a conscious design decision and one which I generally agree with. Safari supports full-screen video, which is the primary reason why I want this, and the full-screen API is a notorious security risk on touchscreen devices even more than traditional computers because you don't have the equivalent of the escape key or the operating system UI giving you a way to tell that the “Please enter your password” dialog which just popped up was generated by the web page and not your OS. On iOS, Safari is already close to full screen anyway so the extra few pixels is less than what you'd need to account for in different screen heights between devices anyway.