Created attachment 8717889 [details] Screenshot Affected versions: 44.0.2 (Build ID: 20160209150140), 45 beta 4 (Build ID: 20160208194709), latest Aurora 46.0a2 and Nightly 47.0a1 (from 2016-02-09) Affected platforms: Mac OS X 10.9.5 Steps to reproduce: 1. Launch Firefox. 2. Open new tabs (Cmd+T) until the overflow scroll buttons are displayed. 3. Enter fullscreen. 4. Exit fullscreen. Expected result: Tabs are properly displayed. Actual result: The last tab is not fully visible. Additional notes: 1. Screenshot attached (note that the behaviour is exactly the same with a clean profile/no theme installed). 2. Not reproducible under Ubuntu 12.04 x64, Windows 10 x86 nor Windows 7 x64. 3. Regression range: Last good revision: d17480aae980fb6b44e68cef9f2aabeac89383f7 First bad revision: 10d47ad00e7a97160d74c5682605c7c82de606d0 Pushlog: https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=d17480aae980fb6b44e68cef9f2aabeac89383f7&tochange=10d47ad00e7a97160d74c5682605c7c82de606d0 Apparently regressed by 10d47ad00e7a Xidorn Quan — Bug 1161802
I cannot reproduce this on OS X 10.10 with either Aurora or Nightly. Is it something specific to 10.9? adalucinet, can you reproduce this on other versions of OS X?
(In reply to Xidorn Quan [:xidorn] (UTC+8) from comment #1) > I cannot reproduce this on OS X 10.10 with either Aurora or Nightly. Is it > something specific to 10.9? adalucinet, can you reproduce this on other > versions of OS X? Sure - just checked on Mac OS X 10.10.5 with latest Nightly 47.0a1 and this issue is reproducible.
xidorn, please let us know if you can repo.
Like comment 1, I still cannot reproduce this issue.
we'd like to confirm this is still around.
(In reply to Jim Mathies [:jimm] from comment #5) > we'd like to confirm this is still around. Yes, this issue is still around - just reproduced it with latest 48.0a1 (from 2016-04-05), under Mac OS X 10.10.5.
Created attachment 8740140 [details] Screen Shot 2016-04-11 at 4.21.25 PM.png I can also reproduce this in 47 on 10.11.4.
Hmmm, wait, so you mean the browser full screen mode, not fullscreen video or something? I misunderstood the scope of this bug.