Closed Bug 363792 Opened 18 years ago Closed 18 years ago

tabbrowser destructor loops over array that's length of tabpanels rather than length of tabs

Categories

(SeaMonkey :: UI Design, defect)

Other Branch
x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: csthomas, Assigned: csthomas)

References

Details

(Keywords: regression)

Attachments

(1 file)

1. Open a new window
2. Open a new tab
3. Close the first tab
4. Close the window


          for (var i = 0; i < this.mTabListeners.length; ++i) {
            this.mPanelContainer.childNodes[i].webProgress.removeProgressListener(this.mTabFilters[i]);


Error: uncaught exception: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIWebProgress.removeProgressListener]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: chrome://global/content/bindings/tabbrowser.xml ::  :: line 2078"  data: no]

I'll have to look at how this should really work.  I'm also curious about the various other loops that loop over listeners.  Do we just have to protect this one with an "if (whatever is not null)" like most of the rest of the loops?
(In reply to comment #0)
>I'm also curious about the various other loops that loop over listeners.
I see none - they all loop over tabs (or their linked browsers).
Attachment #248830 - Flags: review?(neil) → review+
Checking in mozilla/xpfe/global/resources/content/bindings/tabbrowser.xml;
/cvsroot/mozilla/xpfe/global/resources/content/bindings/tabbrowser.xml,v  <--  tabbrowser.xml
new revision: 1.171; previous revision: 1.170
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Component: XP Apps: GUI Features → UI Design
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: