712225 - When element is in fullscreen mode, window.innerHeight is bigger than window.outerHeight

Status: REOPENED

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

Description

[Diogo Golovanevsky Monteiro [:diogogmt]]

Steps to reproduce:
1. Set element into fullscreen mode by calling element.mozRequestFullScreen()
2. Check window.innerHeight and window.outerHeight

Expected results:
window.innerHeight should have the same value as window.outerHeight since the element is in fullscreen mode, or innerHeight should be less than outerHeight, but not bigger.

Actual Results:
window.innerHeight is bigger than window.outerHeight by 6px


*Notes:
-> Here is a screen shot of the inner/outerHeight prior requesting fullscreen on the element: http://diogogmt.files.wordpress.com/2011/12/ff_windowheightinnerouter.png
-> Here is a screen shot of the inner/outerHeight when the element is in fullscreen mode: http://diogogmt.files.wordpress.com/2011/12/ff_windowheightinnerouter_fullscreen.png

Comment 1

[Tim (fmdeveloper)]

Diogo -> Thanks for the report. Can you please provide a public URL or reduced test case that exhibits this issue. Note any changes that have to be made from a fresh profile.

Comment 2

[Diogo Golovanevsky Monteiro [:diogogmt]]

I'm using this example to get the difference between the inner and outer height:
http://diogogmt.github.com/mozilla-central/windowInnerOuterHeight.html

Apparently this bug is being caused by Bug 633602, since I only get the difference between the heights when applying the mouselock patch.

Comment 3

[David Humphrey (:humph)]

Diogo, on OS X I see:

Unlocked/Not-FullScreen:
------------------------

window.outerWidth: 1215 window.outerHeight: 1115
window.innerWidth: 1215 window.innerHeight: 1028

Locked/FullScreen:
------------------
window.outerWidth: 2560 window.outerHeight: 1440
window.innerWidth: 2560 window.innerHeight: 1440

Comment 4

[Emilio Cobos Álvarez (:emilio)]

This is still happening on android, somehow.

Comment 5

[Emilio Cobos Álvarez (:emilio)]

Attachment: testcase with viewport meta tag

Comment 6

[David Lawrence [:dkl]]

Moving all open Core::Widget: Android bugs to GeckoView::General (then the triage owner of GeckoView will decide which ones are valuable and which ones should be closed).

Comment 7

[Emily Toop (:fluffyemily)]

Not applicable to GeckoView

Comment 8

[Emilio Cobos Álvarez (:emilio)]

Why not? I reproduced comment 5 on Fenix.

Comment 9

[[ex-Mozilla] Agi Sferro | :agi]

(In reply to Emilio Cobos Álvarez (:emilio) from comment #8)

Why not? I reproduced comment 5 on Fenix.

sorry we thought if it was a problem it would have been reported somewhere else :) but I guess this bug was the place. Emilio do you have a sense what could be going on here?

Comment 10

[Makoto Kato [:m_kato]]

It might be floating round issue such as bug 1657380.

Comment 11

[Makoto Kato [:m_kato]]

I can reproduce this on Windows 10 + Surface Pro 4 when display's scale setting is 275%.

Comment 12

[Makoto Kato [:m_kato]]

This doesn't depends on Android since I can reproduce this on Windows. I guess that this is same issue as bug 1657380 (mAppUnitsPerDevPixelAtUnitFullZoom isn't float), so I move this to "DOM: Core & HTML" again.