997548 - requestFullScreen mode shows menu bar when cursor moves to top of screen on OSX

Status: NEW

(Core :: DOM: Core & HTML, defect, P5)

Description

[Louis Stowasser [:louisstow]]

No hot-corners or hot-edges. The browser can't intrude on the game experience if the mouse cursor hits the top of the screen. I believe Chrome and Firefox currently both drop down the URL bar when this happens

Comment 1

[Vladimir Vukicevic [:vlad] [:vladv] (needinfo me, slow to respond)]

(In reply to Louis Stowasser [:louisstow] from comment #0)
> No hot-corners or hot-edges. The browser can't intrude on the game
> experience if the mouse cursor hits the top of the screen. I believe Chrome
> and Firefox currently both drop down the URL bar when this happens

Firefox doesn't drop the URL bar down when you're in fullscreen mode (not F11 fullscreen, but actually requestFullScreen()).  So this should already work fine, modulo bug 997537 with multiple monitors.

Comment 2

[Vladimir Vukicevic [:vlad] [:vladv] (needinfo me, slow to respond)]

Ah so this is is an OSX specific problem where fullscreen is broken if the cursor goes to the top of the screen.

Comment 3

[Martin Best (:mbest)]

Here is a video that shows issues in Fullscreen on OSX:  https://www.dropbox.com/s/0bkdx71ir0yhw88/firefox%20osx%20edges.mov

Comment 4

[Olli Pettay [:smaug][[e-mail]]]

Doesn't sound like a DOM issue but Widget level or toolkit/firefox.

Comment 5

[Steven Michaud [:smichaud] (Retired)]

This is just how fullscreen mode works on OS X.

This isn't a bug, it's a feature :-)

Comment 6

[Markus Stange [:mstange]]

With element mouse capturing (as proposed in bug 997544) we could turn off hot edges as long as the mouse is captured to any element.

Comment 7

[Steven Michaud [:smichaud] (Retired)]

(Following up comment #5)

There may be a way to turn off this "feature" -- it if exists it'll be OS-specific and probably undocumented.  But before I look for one I'd need at least one example of a Mac app that uses native fullscreen mode and *doesn't* show the menubar when you mouse over where it's normally displayed.

Comment 8

[Steven Michaud [:smichaud] (Retired)]

> No hot-corners or hot-edges.

What exactly are you referring to here?  Something OS-specific?

Comment 9

[Markus Stange [:mstange]]

(In reply to Steven Michaud from comment #7)
> (Following up comment #5)
> 
> There may be a way to turn off this "feature"

Maybe [NSApp setPresentationOptions:NSApplicationPresentationHideMenuBar | ...] can do it?

> But before I look for one I'd need
> at least one example of a Mac app that uses native fullscreen mode and
> *doesn't* show the menubar when you mouse over where it's normally displayed.

Antichamber is an example, though it also uses pointer lock, so maybe the invisible mouse pointer can never really touch the top edge of the screen. Anyway, that's not really the point - games need the ability to turn off the menu bar, and we should give them that option. If that means using "non-native" fullscreen for them, then I think that's what we should do.

(In reply to Steven Michaud from comment #8)
> > No hot-corners or hot-edges.
> 
> What exactly are you referring to here?  Something OS-specific?

Different OSes have different behaviors in the corners or at the edges. This bug asks for an option to disable all of them. On Mac that's just the menubar hot edge at the top.

Comment 10

[Steven Michaud [:smichaud] (Retired)]

(In reply to comment #9)

> If that means using "non-native" fullscreen for them, then I think
> that's what we should do.

I don't have any objection to this.  But people will need to
understand what it means.  In particular they'll need to be able to do
without any other native-fullscreen-specific features (whatever they
might be).

>> There may be a way to turn off this "feature"
>
> Maybe [NSApp
> setPresentationOptions:NSApplicationPresentationHideMenuBar | ...]
> can do it?

This'd be worth looking into, if people feel the need.

Comment 11

[Firefox Bug Husbandry Bot]

https://bugzilla.mozilla.org/show_bug.cgi?id=1472046

Move all DOM bugs that haven’t been updated in more than 3 years and has no one currently assigned to P5.

If you have questions, please contact :mdaly.