Open Bug 487892 Opened 11 years ago Updated 7 months ago

Support translucent nav-bar and tab-bar in fullscreen mode

Categories

(Firefox :: Toolbars and Customization, enhancement)

enhancement
Not set

Tracking

()

UNCONFIRMED

People

(Reporter: samwyse, Unassigned)

Details

Attachments

(1 file)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.8) Gecko/2009032609 Firefox/3.0.8
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.8) Gecko/2009032609 Firefox/3.0.8

If you move the mouse to the top of the screen in fullscreen mode, the nav-bar and tab-bar drop down, shifting the rest of the screen downwards.  I find having the page bounce up and down is incredibly annoying, especially if I'm trying to click on a link at the top of the web-page and I overshoot.  I'd like to see an option to make the nav-bar and tab-bar translucent and not shift the screen.  See the attachment.

Reproducible: Always

Steps to Reproduce:
1.  Enter fullscreen mode
2.  Move mouse to top of screen
3.  Move mouse away
I came here to suggest exactly the same.

Another method of improving this would be to increase the length of time the cursor has to be at the top of the screen before the tabs/address bar show up?

In general if I'm in fullscreen mode it means I don't plan on changing anything in the address bar or flicking to different tabs so the top bar appearing 'accidentally' when clicking a link near the top can be quite annoying.

Yes I am fully aware that this is my own unique usage-scenario :)  However, if there was a 1 second (or maybe even half second) requirement for the cursor to be at the top before the bar appears then it'd dramatically reduce the number of 'accidental' appearances of the nav bar when trying to get a link near the top of the page.

Also, as suggested, for the nav bar to fade into view OR for the nav bar to still drop down but be 'above' the page (i.e. covers top of page so the page doesn't jump around as much) then it'd be less obtrusive too.
You need to log in before you can comment on or make changes to this bug.