Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I'm trying to indicate that I'm using your words. I have roughly zero experience with macos, and I don't know what native fullscreen means. In windows, I don't think browsers use any separate apis for rendering fullscreen, so I just don't really understand it.

> one of them is supported on macOS

Assuming "support" means it actually works, there seems to be conflicting information about which one is actually supported.




It seems that in some cases, the way Firefox is calling those APIs is incorrect, or causes undesirable behavior.


Who the fuck knows what's happening in Wowfunhappy's screenshot. I doubt it's because of the native fullscreen because it's something that's been a part of macOS for the past 8 years. And again, Firefox is already using the native fullscreen functionality in some cases. The issue is that some of the time it's not actually a fullscreen application and is merely just pretending to be one.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: