612054 - Holding Ctrl+T down can create tabs way too quickly

Status: RESOLVED WONTFIX

(Firefox :: Tabbed Browser, defect)

Description

[Matheus Kerschbaum]

User-Agent:       Mozilla/5.0 (Windows NT 6.1; rv:2.0b8pre) Gecko/20101113 Firefox/4.0b8pre
Build Identifier: Mozilla/5.0 (Windows NT 6.1; rv:2.0b8pre) Gecko/20101113 Firefox/4.0b8pre

Simply holding Ctrl+T down can create tabs at a rate of about 100 tabs per second on my PC. This is absurd since there may be users who want to create several blank tabs sometimes and if they miss-use Ctrl+T they can end up with several hundred tabs.

Reproducible: Always

Steps to Reproduce:
1.Hold down Ctrl+T
2.Be amazed
Actual Results:  
Firefox creates hundreds of blank tabs.

Expected Results:  
Firefox should create new tabs at a reasonable rate (i.e 10 tabs per second).

Since this is a "If I do something stupid, something stupid happens" type of bug, I don't think it should block release.

Comment 1

[pal-moz]

(In reply to comment #0)
> Expected Results:  
> Firefox should create new tabs at a reasonable rate (i.e 10 tabs per second).

both hit ctrl+T and hold ctrl+T should create only 1 new tab ? (not per second)
no need to create so many new tabs ?

Comment 2

[Scott A.]

(In reply to comment #1)
> (In reply to comment #0)
> > Expected Results:  
> > Firefox should create new tabs at a reasonable rate (i.e 10 tabs per second).
> 
> both hit ctrl+T and hold ctrl+T should create only 1 new tab ? (not per second)
> no need to create so many new tabs ?

I'd prefer it only add 1 tab, but if it were kept as adding tabs it should be far less than 10/sec, 1 per second maximum. This bug should definitely be blocking2.0.

Comment 3

[imradyurrad]

What's the point of this bug? No reasonable person would sit around holding Ctrl+T all day.

The solution would be to not "miss-use Ctrl+T".

Comment 4

[Fritz]

(my pitch for marking this 'wontfix')

1) There is a limited use case: Sometimes when I want to obfuscate tab titles I will hold down Ctrl+T until they have scrolled off the screen and then use Ctrl+1 to navigate back to tabs and Ctrl+9 to get to the last new tab.
2) It's expected behavior.  Ctrl+W closes tabs at a standard refresh rate which is great for closing large numbers of recently opened tabs quickly (important for someone with the propensity to open 25+ tabs when reading the morning news).  Ctrl+T should be at the same rate rather than confuse expectations.
3) All other reasons aside with limited arguments to go either way: dev and reviewer time is precious and needn't be wasted coding changes for an extremely marginal case.