Closed Bug 197658 Opened 21 years ago Closed 19 years ago

ctrl-tab in gtk2 build repeatedly cycles through tabs instead of skipping to next tab

Categories

(Core Graveyard :: GFX: Gtk, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: ash, Assigned: blizzard)

References

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030313
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030313

I use tabbed browing a lot, and sometimes when i try to go from one tab to the
next using ctrl-tab or to the previous using shift-ctrl-tab, mozilla starts
cycling through the tabs.  eventually it stops, but usually not before skpping
over at least 5 tabs.

usually this happens when i have 7 tabs open and i'm on the 4th, linuxtoday.com,
and i'm trying to get to the 5th, slashdot.org.  i hit ctrl-tab and instead of
skipping to the very next tab, mozilla goes to the next tab, then goes to tab 6,
7, 1, 2, and eventually it stops on a somewhat random tab.  this is not 100%
reproducible, but it happens maybe every other or every 3rd time i try to switch
between these 2 tabs.  Switching between other tabs seems to trigger the problem
less frequently.

i'm using the 1.3 release rpms for rh 8.0, gtk2 on an rh8.0 system.  the same
problem happened with 1.3b.

Reproducible: Sometimes

Steps to Reproduce:
1.
2.
3.
Blocks: gtk2
here's the deal:  This bug was really easy for me to reproduce using every
redhat 8 kernel or kernel update, but now that i've upgraded to a 2.5.66
self-built kernel, it's impossible to reproduce.  i'm not going back to 2.4 i
don't think, so i'm no longer personally concerned about this bug.  but if
someone needs help reproducing it, let me know and i can reboot.
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/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.