2 ms·

> And as I already mentioned, the current Firefox implementation is just downright broken. Yes, and as others mentioned, the "native" implementation in Firefox

> And as I already mentioned, the current Firefox implementation is just downright broken. Yes, and as others mentioned, the "native" implementation in Firefox is also downright broken. Without knowing which one is more broken, there doesn't seem to be a strong reason to change the default. I understand that the native one works better for you, but you're not the only user.

Hamuko 7y ago
The strong reason to change the default is that only one of them is supported on macOS and it's the one that's not default. Not to mention the fact that Firefox already uses the native fullscreen functionality. It just doesn't use it fully and consistently. And what's with the quotes around native?
- recursive 7y ago
  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.
  - Hamuko 7y ago
    Support means that Apple has APIs for it. https://developer.apple.com/documentation/appkit/nswindowdelegate/1419563-windowwillenterfullscreen?language=objc https://developer.apple.com/documentation/appkit/nswindowdel...
    - recursive 7y ago
      It seems that in some cases, the way Firefox is calling those APIs is incorrect, or causes undesirable behavior.
      - Hamuko 7y ago
        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.

Hamuko 7y ago

The strong reason to change the default is that only one of them is supported on macOS and it's the one that's not default. Not to mention the fact that Firefox already uses the native fullscreen functionality. It just doesn't use it fully and consistently. And what's with the quotes around native?

recursive 7y ago
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.
- Hamuko 7y ago
  Support means that Apple has APIs for it. https://developer.apple.com/documentation/appkit/nswindowdelegate/1419563-windowwillenterfullscreen?language=objc https://developer.apple.com/documentation/appkit/nswindowdel...
  - recursive 7y ago
    It seems that in some cases, the way Firefox is calling those APIs is incorrect, or causes undesirable behavior.
    - Hamuko 7y ago
      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.