javascript error in tabbrowser.xml: Rapidly closing two tabs manually doesn't work

RESOLVED EXPIRED

Status

SeaMonkey
Tabbed Browser
--
minor
RESOLVED EXPIRED
16 years ago
8 years ago

People

(Reporter: WeirdAl, Unassigned)

Tracking

Trunk
x86
Windows 98

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

16 years ago
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.7+) Gecko/20020108
BuildID:    Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.7+) Gecko/20020108

When I have multiple tabs open, and I want to close 2 of them without closing
all of them, I cannot do so quickly.  I receive a JavaScript error if I attempt
to close the second one too soon after the first one closes.

Reproducible: Sometimes
Steps to Reproduce:
1. Open two new tabs.
2. Switch to other tabs, then back to one of the new tabs, then to the other.
3. Right-click on tab, select "Close Tab".  Very quickly after that, right-click
on the other new tab, select "Close Tab".

Actual Results:  Error: aTab has no properties
Source File: chrome://global/content/bindings/tabbrowser.xml#tabbrowser.removeTab()
Line: 2

Expected Results:  Both tabs close.

Updated

16 years ago
Summary: Rapidly closing two tabs manually doesn't work: JS error → javascript error in tabbrowser.xml: Rapidly closing two tabs manually doesn't work

Comment 1

16 years ago
Reassigning to new component owner.
Assignee: hyatt → jaggernaut

Comment 2

16 years ago
-> future
Target Milestone: --- → Future
QA Contact: sairuh → pmac
(Assignee)

Updated

10 years ago
Product: Core → SeaMonkey
Assignee: jag → nobody
QA Contact: pmac → tabbed-browser
Target Milestone: Future → ---

Comment 3

9 years ago
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED

Comment 4

8 years ago
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.