User Agent: Mozilla/5.0 (Android; Tablet; rv:28.0) Gecko/28.0 Firefox/28.0 (Nightly/Aurora) Build ID: 20140321152412 Steps to reproduce: 0. I tried this on a Nexus 7 (2013) with the normal Firefox app and also the Beta app from the Play store. 1. Install add-on "Full Screen" (or "Quick Gestures") to get fullscreen capability. 2. Deactivate auto-hide of the title bar ("Scroll title bar" in Settings > Display). 3. Load a long page, e.g. http://en.m.wikipedia.org 4. Activate fullscreen mode (via one of the abovementioned add-ons). 5. Deactivate fullscreen mode. Actual results: The top of the page gets cut-off as if the page is underneath the titlebar. E.g. with the mobile wikipedia site the search at the top of the page is not accessible anymore. Expected results: The page should be rendered starting below the title bar, as usual.

Thanks for the bug report. This is reproducible on my Nexus 5 (Android 4.4.2). I'll attach a screenshot describing the difference.

Left side is full-screen mode. Right side is non full-screen mode. When exiting out of full-screen mode, the page doesn't reposition itself under the title-bar. Instead, it's fitted behind it.

Is it possible to reproduce this without using an add-on? i.e. using the mozRequestFullScreen API from a webpage?

Answer to comment #3: Yes. If I understand you correctly, https://developer.mozilla.org/samples/domref/fullscreen.html should be a valid test. I used the FF beta app (29.0), uninstalled all add-ons and entered fullscreen after a long press on the video element, then immediately used the back button to exit fullscreen. The result is the same: After this procedure the first line vanishes "behind" the title bar.

Thanks, that exactly what I wanted to know!

filter on [mass-p5]

Bug still present in Firefox 37.0.

In the latest Nightly with bug 1180295 and bug 1197233, the STR from comment 4 are fixed, mostly. After exiting fullscreen the first line is still behind the url bar, but the page is scrollable and can be scrolled to reveal that top line. So that bit is no longer "inaccessible" at least. I'm going to close this as fixed; if you can still reproduce on Nightly please reopen.

FYI, I can reproduce this issue (or a very similar one) when back from a full-screen YouTube video: bug 1379628.