317425 - At Google's personalize home page - Right Click menu on a link opens the link in the current window and shows menu. Should only show the menu

Status: RESOLVED INVALID

(Firefox :: Tabbed Browser, defect)

Description

[Steven Scott]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051111 Firefox/1.5
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051111 Firefox/1.5

I logged into my home page at google.  I have Motley Fool and Slashdot listed with 9 entries for Slashdot and 6 for Motley fool.  When I right click on either the Slashdot or Motley fool title to open the link in a new tab, the link is launched into the current tab.
Also, if I control and click to launch the link in a new tab, it opens in the same tab.  This feature works normally on this page and others, just not the google home page.

Reproducible: Always

Steps to Reproduce:
1. Sign into your Google Home Page
2. Right Click on Slashdot feed on the 'Slashdot' title
3.

Actual Results:  
Link is opened in the current tab and the right click menu is shown.  Only the right click menu should be shown.

Expected Results:  
Just the right click menu should be shown.

The Control-Right Click on the Slashdot title does not always load the page in a new tab.  Quite often, but not always, it loads it in the current tab.

Comment 1

[Steven Scott]

Attachment: Screen shots of the problem

Image 1 showing the position of the click

Comment 2

[Steven Scott]

Attachment: Screen shots of the problem

Image 2 showing the right click menu and the loading happening

Comment 3

[Steven Scott]

Attachment: Screen shots of the problem

Image 3 showing the result with Slashdot loaded

Comment 4

[Kevin Brosnan]

You have quite a number of extensions installed try reproducing this in Firefox's safe-mode or a new profile.

http://kb.mozillazine.org/Safe-Mode
http://kb.mozillazine.org/Profile_Manager

Comment 5

[Steven Scott]

I ran FireFox in Safe Mode with the exact same result.

Comment 6

[Steven Scott]

Bug was in Google javascript and has been fixed.