265626 - Ctrl-click on links opens in same tab when PC is busy

Status: RESOLVED DUPLICATE of bug 145313

(Core :: DOM: UI Events & Focus Handling, defect)

Description

[kosta_kp]

User-Agent:       Mozilla/5.0 (Windows; U; Win98; rv:1.7.3) Gecko/20041001 Firefox/0.10.1
Build Identifier: Mozilla/5.0 (Windows; U; Win98; rv:1.7.3) Gecko/20041001 Firefox/0.10.1

Often, when there are pages loading in other tabs, or when the CPU is otherwise
in  use, Firefox ignores the CTRL part of CTRL-Clicking and opens links in the
same tab. (This may be true for SHIFT-Clicking as well, but I don't use that
very much, so I don't know.) This has been a problem for a while (I think I've
been using Fire____ since 0.8 or earlier).
It may just be that I'm using an old 400 Mhz Celeron with 192 MB RAM, but I'm
not sure.

Reproducible: Always
Steps to Reproduce:
1. Get a lot of pages loading in different tabs simultaneously (helps to be on a
slow connection) OR have some other programs running in the background.
2. CTRL-Click on any ol' link on a web page.
Actual Results:  
Opened the link in the same tab.

Expected Results:  
Opened the link in a NEW tab.

Comment 1

[Aaron Leventhal]

Ah, is that what's going on! Anyway this isn't really keyboard navigation.

Comment 2

[Jesse Ruderman]

I've had similar problems in Thunderbird (Ctrl+click while busy is interpreted
as a normal click).

Comment 3

[Jesse Ruderman]

Attachment: testcase

Comment 4

[Jesse Ruderman]

*** Bug 268924 has been marked as a duplicate of this bug. ***

Comment 5

[Jesse Ruderman]

*** Bug 272339 has been marked as a duplicate of this bug. ***

Comment 6

[Aaron Leventhal]

*** Bug 271837 has been marked as a duplicate of this bug. ***

Comment 7

[Torben]

I see this on a current Camino nightly too.

Comment 8

[Dev]

I have faced same problem on a couple of windows systems (2k and xp pro, both with 512 MB memory). When the website is not finished loading, ctrl+clicking on a link hangs the browser for a second and then opens it in the same tab instead of opening in a new one. Happens to me usually on complex websites like slashdot but not limited to them. Faced it on 1.x as well as the 2.0 release.

Right clicking and going to 'Open Link in new Tab' works correctly though. (Number of open tabs may be a factor as I usually surf with minimum 8-10 tabs open) I am sure extensions are not the reason here since there are no extensions installed on the XP Pro machine.

[one kind of related issue: on Slashdot, a lot of times when the page has not finished loading, clicking on a reply opens a blank page with only one word "false", instead of expanding it . Not sure if it is an issue with Firefox or the new discussion format on /.]

Comment 9

[Mikel Ward]

See bug 145313 for more details.

Comment 10

[mr]

I believe this is the same problem as in 
Bug 334497 – "click processing doesn't use shift/modifier at click time, checks at processing time".
I posted an extended description there. Please check it out.

Comment 11

[Henry Hartley]

As [e-mail] says, this is more a matter of the control key being lifted before Firefox responds to the ctrl-click.  If, when you ctrl-click on a link, you continue to hold down the control key the new tab will eventually open with the linked document.  The problem reported here, as far as I know, only happens if you release the control key before the new tab has appeared.

I would say, however, that this bug (and possibly 334497) should be marked as a duplicate of 145313 instead.  This is the older bug and is against core / event handling rather than 334497's mail component.  Also, 334497 is listed as unconfirmed while 145313 is NEW.

Comment 12

[Serge Gautherie (:sgautherie)]

[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a5pre) Gecko/20070515 SeaMonkey/1.5a] (nightly) (W2Ksp4)

I can reproduce the
"start holding ctrl after clicking the second button, you'll get "true" incorrectly."
case,
however it's rather difficult on my fast computer.

***

R.Duplicate

Reopen if you think this bug has a different cause.

Comment 13

[Serge Gautherie (:sgautherie)]

(In reply to comment #12)
> I can reproduce the

Actually, it's hard to tell:
maybe I'm just press the key before actually releasing the mouse button :-/

We would probably need a test case with a time delay or something, to be sure.