Open Bug 703367 Opened 13 years ago Updated 2 years ago

When using fullscreen API, element does not fill up screen on secondary monitors

Categories

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

Product:
Core
Component:
DOM: Core & HTML
Platform:
x86
macOS
Type:
defect

Tracking

()

People

(Reporter: jlong, Unassigned)

References

Details

Attachments

(2 files)

Space for statusbar that doesn't exist on second monitor
109.68 KB, image/png
Details
Tabs got weird after multiple fullscreen changes and resolution changes
37.41 KB, image/png
Details 
If I put an element fullscreen, Firefox leaves spaces for the menu bar even on secondary monitors where the menu bar doesn't exist. This happens on secondary monitors. Screenshot attached.

I don't file bugs for Firefox very much, so please tell me what information I need to provide.

Build: Nightly 2011-11-14
Platform: OS X 10.6
You might not see if very will in the pic, but there's a row of whitespace at the top where the menubar usually is.
Can you post a link to the web page (or upload the page's HTML) which exhibits this problem please?
Component: General → DOM: Core & HTML
QA Contact: general → general
I don't have my secondary monitor hooked up right now, but I'd imagine it would happen on any fullscreen demo:

http://html5-demos.appspot.com/static/fullscreen.html

I push my demo where I definitely saw this later today.
WFM on Windows 7 x64 Nightly 2011-11-16.
Probably more of a Mac widget bug.
I can't repro this on my old MacOSX 10.5 mini. I have no hardware which can repro this bug, help wanted...
I don't have the hardware to repro this bug either.  But bgirard might ...
Hey guys,

Here's the demo I made where I found the problem: http://jlongster.com/2011/11/21/canvas.html

It also happens with this demo: http://html5-demos.appspot.com/static/fullscreen.html

I made a movie explaining how I reproduce the bug:

http://jlongster.com/s/fullscreen-bug.mov
James, what are the resolutions of your two monitors?

I just tried this on my 2-monitor setup (internal mbp 1920x1200 and external 1600x1200) and I can't reproduce the problem on either of the demos linked from comment 8.
Dell monitor is 1680x1050 and mbp is 1440x900.

It appears to only happen when my Dell monitor is the main monitor (in the Displays > Arrangement I dragged the menu bar to it), and the mbp is the secondary monitor. It happens on the mbp at that point.

It works fine on *both* monitors if I make the mbp the main monitor.
> It works fine on *both* monitors if I make the mbp the main monitor.

Ah, that's the configuration I was testing before.

But I can't reproduce the problem even if I move my menubar to the external monitor....
(In reply to Boris Zbarsky (:bz) from comment #11)
> > It works fine on *both* monitors if I make the mbp the main monitor.
> 
> Ah, that's the configuration I was testing before.
> 
> But I can't reproduce the problem even if I move my menubar to the external
> monitor....

Are you on nightly? Mac OS X 10.6? Not sure what else to pinpoint.
I'm on 10.6.8, with a Nov 20 nightly.

The other obvious difference is that my two monitors have the same height and yours don't, but your screenshot is not showing a 240px tall white rectangle....
Ok, something is definitely off.

I tried changing the resolution of mbp as a second monitor, and it actually fixed the issue. Even when changing the resolution back to 1440x900, the bug disappeared.

But then I reloaded the page and it would happen again. I tried changing resolutions again and now my tabs got crunched (see screenshot).

I know this is vague, but it's difficult to find consistent reproducibility.
(In reply to Steven Michaud from comment #7)
> I don't have the hardware to repro this bug either.  But bgirard might ...

I'm back on Friday, I can have a look then.
I still see this bug in Nightly versions of Firefox. The white gap at the top where the OS X bar usually is.
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.
Priority: -- → P5
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: