ctrl+t new tab hotkey becomes disabled after clicking "show quoted text" in Google groups




Tabbed Browser
13 years ago
12 years ago


(Reporter: Don Jackson, Assigned: Ben Goodger (use ben at mozilla dot org for email))


1.5.0.x Branch
Windows XP

Firefox Tracking Flags

(Not tracked)





13 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2

View a Google Groups archived discussion like the one at the link above.  Click
on "Show Quoted Text".  The new tab hotkey (ctrl+T) is disabled.  The menu and
ctrl_clicking still work to open new tabs.

Reproducible: Always

Steps to Reproduce:
1. View a Google Groups archived discussion like the one at the link above.
2. Click on "Show Quoted Text".
3. Try to press CTRL+T to open a new tab.

Actual Results:  
Nothing (no tab opened).

Expected Results:  
A new tab should have opened.
WFM Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050331

Try updating to one of the nightly builds used for testing purposes. These are
relatively reliable and are available at the bottom of this page...

...hrm... When I open a new tab to pull up the bookmarked page, the address bar
no longer displays anything. Click on "Nightly Builds" at developer.mozilla.org
to get a night build. I'm off to submit another report for 20050331.
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 3

12 years ago
I've downloaded several nightly build during reseaching this.  I can reproduce
this error in the latest versions of 1.0.7+ and the 1.5 beta 1 of Firefox.  It
is a minor bug, but it affects me quite often in the tasks I perform with Firefox.

Pick any Google Groups article with the "Show Quoted Text" link to anchor and
click it.  Ctrl+T will not open a new tab until after you click somthing else...
 It may do this for other links to anchors in DHTML code.

Comment 4

12 years ago
I think this is a conflict with JavaScript. The workaround is pressing the tab key   for facilitate the detection of Ctrl-t and other keyboard shortcuts to Firefox.

Comment 5

12 years ago
I can confirm this bug to exist in FF 1.5. I also suspect it to be related to JavaScript as I find JS to be in all those pages when I experience this problem.
Any CTRL+<key> input should be handled independently from the content viewed - or better to say, I cannot think of anything that is browsable and that makes use of CTRL+<key> input.
The only workaround I know of is to select "New Tab" from File menu.

Comment 6

12 years ago
WFM Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060120 Firefox/1.6a1 ID:2006012005


12 years ago
Last Resolved: 12 years ago
Resolution: --- → WORKSFORME
Version: unspecified → 1.5.0.x Branch
<- Verified w/
You need to log in before you can comment on or make changes to this bug.