363296 - Google large icon is misplaced when used as home page and tab-bar is always displayed.

Status: RESOLVED DUPLICATE of bug 347046

(Firefox :: Tabbed Browser, defect)

Description

[Dan Cornett]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1) Gecko/20061010 Firefox/2.0
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1) Gecko/20061010 Firefox/2.0

I have www.google.com as my home page.  If I enable the preference to always show the tabs bar, then when firefox 2.0 starts up the large Google graphic is not positioned correctly -- it displays at the top right of the window (overlapping the tab bar) not at the center of the web page.

A refresh of the window, and all subsequent access to google.com display fine; it only happens as part of initial startup.

It does not happen if the "always show the tab bar" is not checked.

It does not happen by creating a new tab.

It seems to be rather specific to startup with the tab bar enabled.

(Speculation: a race condition?)

I'm not sure, but I think this was present the first time I started Firefox 2.0 (just did today).  However, I did go, after the initial startup (which, of course, took me to the Mozilla page), download & install the Google browser-sync addition.

This happens with the only installed add-ons are DOM Inspecter 1.8.1 and Talkback 2.0.

Reproducible: Always

Steps to Reproduce:
1. Enable (check) the preference "always show the tab bar".
2. Set www.google.com as default (home) page.
3. Quit Firefox, then restart it.


Actual Results:  
Large "Google" icon is misplaced.

Expected Results:  
graphic to be properly placed (as it is after a refresh of the page)

Have tried this (and acts the same) on both an iBook G4 and an eMac (both at OS/X 10.4.8).

Comment 1

[Phil Ringnalda (:philor)]

Even though it doesn't sound like your problem at the start, see bug 347046 comment 18 and on.

*** This bug has been marked as a duplicate of 347046 ***

Comment 2

[Dan Cornett]

The reference duplicate bug is NOT fixed at this time (though it does appear to be the same bug - that I agree with).