If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

clicking on "X" sometimes closes two tabs instead of one

RESOLVED EXPIRED

Status

SeaMonkey
Tabbed Browser
RESOLVED EXPIRED
14 years ago
9 years ago

People

(Reporter: christopher kriese, Unassigned)

Tracking

Trunk
x86
Windows XP

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

14 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5a) Gecko/20030728 Mozilla Firebird/0.6.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5a) Gecko/20030728 Mozilla Firebird/0.6.1

When clicking on the "X" to close the current tab (the one "on top" or active),
the browser should close only that tab.  However, sometimes if closes two tabs.
I have not been able to determine a pattern for when it closes the two instead
of one tab. However, it does this rather frequently...approx. 30% of each click
on the "X".

Reproducible: Sometimes

Steps to Reproduce:
1. Open several tabs in the brower (4 or more)
2. Click on the right most tab
3. Click on the "X"
4. Continue clicking and count the number of open tabs

Actual Results:  
Sometimes, the browser properly closes one tab, but sometime it closes two tabs

Expected Results:  
It should only close one tab at a time and that should to be top tab.  Then,
based on whatever rules that mozilla uses, it should another tab "on top".

Comment 1

14 years ago
Sure you aren't somehow issuing a double-click?
If so, this would be fixed by a fix for bug 187199

Comment 2

14 years ago
*** Bug 243594 has been marked as a duplicate of this bug. ***
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
Last Resolved: 12 years ago
Resolution: --- → EXPIRED
Product: Core → SeaMonkey
You need to log in before you can comment on or make changes to this bug.