3 ms·

>What do you find is broken about Firefox's default state? Firefox uses a self-made fullscreen implementation by default on macOS, which is buggy and causes me

by Hamuko 7y ago

>What do you find is broken about Firefox's default state? Firefox uses a self-made fullscreen implementation by default on macOS, which is buggy and causes menubar issues. Firefox has code to use the macOS native fullscreen feature, but it's actually hidden behind "full-screen-api.macos-native-full-screen" about:config flag. So if you're on macOS and want to fullscreen something on another monitor (and actually have it work proper), you need to figure out that the fix is hidden there.

coldpie 7y ago
Surely you can understand that an issue in a platform-specific implementation of a fairly obscure feature doesn't really support your assertion that it is "broken out of the box". It's likely that config option is not set by default because it's known to be buggy in some other way. You can read some discussion of this setting here, which has seen some activity in the past year, so it is being worked on: https://bugzilla.mozilla.org/show_bug.cgi?id=1403085 https://bugzilla.mozilla.org/show_bug.cgi?id=1403085
- Hamuko 7y ago
  A fairly obscure feature, what? Fullscreen is a fairly obscure feature?
Wowfunhappy 7y ago
Uh, this was the first I'd heard about this setting, so I went ahead and tried it. I don't know what's happening for you, but when I toggle that setting, full-screen becomes quite broken: https://i.ibb.co/7tJYHPf/Screen-Shot-2020-04-10-at-9-30-25-AM.png https://i.ibb.co/7tJYHPf/Screen-Shot-2020-04-10-at-9-30-25-A... (Note all the empty space at the top and bottom.) Breaks the fullscreen animation too. I don't have problems with the standard full screen in Firefox—I never knew it wasn't using the native mac method—although I only have one monitor. The one big problem I do have with Firefox on Mac is that it intercepts the system keyboard shortcuts. So if you set up custom keyboard shortcuts in System Preferences for menu items, they won't work in Firefox.
- Hamuko 7y ago
  That's not happening to me with full-screen-api.macos-native-full-screen and single screen.
  - recursive 7y ago
    Still though, you can probably understand now why it's not the default.
    - Hamuko 7y ago
      I can't actually for a myriad of reasons. Not only has the native fullscreen functionality been around for years (eight to be exact), it's pretty mature. Other applications, like mpv, have migrated over to the native fullscreen functionality just fine. And as I already mentioned, the current Firefox implementation is just downright broken.
      - recursive 7y ago
        > 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.

by Hamuko 7y ago

coldpie 7y ago

Surely you can understand that an issue in a platform-specific implementation of a fairly obscure feature doesn't really support your assertion that it is "broken out of the box". It's likely that config option is not set by default because it's known to be buggy in some other way. You can read some discussion of this setting here, which has seen some activity in the past year, so it is being worked on: https://bugzilla.mozilla.org/show_bug.cgi?id=1403085 https://bugzilla.mozilla.org/show_bug.cgi?id=1403085

Hamuko 7y ago
A fairly obscure feature, what? Fullscreen is a fairly obscure feature?

Wowfunhappy 7y ago

Uh, this was the first I'd heard about this setting, so I went ahead and tried it. I don't know what's happening for you, but when I toggle that setting, full-screen becomes quite broken: https://i.ibb.co/7tJYHPf/Screen-Shot-2020-04-10-at-9-30-25-AM.png https://i.ibb.co/7tJYHPf/Screen-Shot-2020-04-10-at-9-30-25-A... (Note all the empty space at the top and bottom.) Breaks the fullscreen animation too. I don't have problems with the standard full screen in Firefox—I never knew it wasn't using the native mac method—although I only have one monitor. The one big problem I do have with Firefox on Mac is that it intercepts the system keyboard shortcuts. So if you set up custom keyboard shortcuts in System Preferences for menu items, they won't work in Firefox.

Hamuko 7y ago
That's not happening to me with full-screen-api.macos-native-full-screen and single screen.
- recursive 7y ago
  Still though, you can probably understand now why it's not the default.
  - Hamuko 7y ago
    I can't actually for a myriad of reasons. Not only has the native fullscreen functionality been around for years (eight to be exact), it's pretty mature. Other applications, like mpv, have migrated over to the native fullscreen functionality just fine. And as I already mentioned, the current Firefox implementation is just downright broken.
    - recursive 7y ago
      > 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.