274991 - Tab bar always visible in fullscreen

Status: RESOLVED INVALID

(Firefox :: Toolbars and Customization, defect)

Description

[Mathieu Johnson]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a6) Gecko/20041215 Firefox/1.0+
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a6) Gecko/20041215 Firefox/1.0+

When I have more than one tab opens (or when the tab bar is visible) and I go in
fullscreen mode, the tab bar is always visible.

In Firefox 1.0, the tab bar was not visible in fullscreen mode so I guess it's a
regression because, with the new behavior, you don't get a "true" fullscreen mode.

Reproducible: Always

Steps to Reproduce:
1. Open Firefox
2. Open a new tab so that the tab bar is visible
3. Go to fullscreen mode with F11

Actual Results:  
Tab bar is still visible

Expected Results:  
Tab bar would not be visible like every othe toolbars (except the find toolbar)
and firefox would provide true fullscreen

Comment 1

[Phil Ringnalda (:philor)]

Unable to reproduce that being a regression: new 1.0 profile, Ctrl+T, F11, the
tab bar shows.

Comment 2

[Mathieu Johnson]

Ok my bad, so maybe it was always was like this.

I had an extension installed for as long as I remember using Firefox and Mozilla
called Autohide so it would autohide bars.

This extension is not working correctly in newer trunk builds so the tab bar
does not autohide. (the other toolbars are ok)

I could file a bug with a better summary because I think that is the behavior
most people expect from the fullscreen feature. No toolbars visible in
fullscreen mode. 

I also think an autohiding feature like IE or the autohide extension is expected
by most people and should ideally get in the base product. I'll look for a bug
on that and file one (as enhancement) if I don't find one

Feel free to close this bug.

Comment 3

[Nickolay_Ponomarev]

The idea of having the tabbar always visible makes sense to me, so closing this
as invalid. You may open a bug on making it not visible in fullscreen by
default, but I think it will be wontfix'ed.