Closed Bug 547535 Opened 16 years ago Closed 16 years ago

Tabbed windows don't close

Categories

(SeaMonkey :: Tabbed Browser, defect)

x86_64
macOS
defect
Not set
major

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: quicksilver8, Unassigned)

Details

User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; it; rv:1.9.3a2pre) Gecko/20100221 SeaMonkey/2.1a1pre Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; it; rv:1.9.3a2pre) Gecko/20100221 SeaMonkey/2.1a1pre When I open several tabbed window in browser, clicking on x button on the right doesn't shut the tab, nor works command key, nor menu item File->Close Tab. To come back a 1-tab window, I need to close SeaMoneky and relaunch. This happen on my MacBook with Snow Leopard; with my Quicksilver G4 and Leopard, it's OK. Reproducible: Always
[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.3a2pre) Gecko/20100220 SeaMonkey/2.1a1pre] (nightly) (W2Ksp4) WorksForMe. ***** Is that really a 64-bit build? OS? Do you get any entry in the Error Console? Can you reproduce with SeaMonkey v2.0.3?
Severity: normal → major
Version: unspecified → Trunk
This problem occurs for me as well on OS X 10.5 and 10.6 for both PowerPC and x86 with the latest (20100223 SeaMonkey/2.1a1pre) nightly builds. I do not see this problem when running this build on Windows NT 6.1 or Linux (on x86_64).
Sherman: Do you see any errors/warnings in the Error Console (Tools->Web Development->Error Console) when clicking on the close button of a tab? Click on "Clear" button in the Error Console before testing this so that you have no unrelated messages in the error console.
Here are the errors I get when I open a new tab: Error: uncaught exception: [Exception... "Cannot find interface information for parameter arg 0 [nsIDocShell.contentViewer]" nsresult: "0x80570006 (NS_ERROR_XPC_CANT_GET_PARAM_IFACE_INFO)" location: "JS frame :: chrome://navigator/content/tabbrowser.xml :: updateTitlebar :: line 759" data: no] Error: uncaught exception: [Exception... "Cannot find interface information for parameter arg 0 [nsIDocShell.contentViewer]" nsresult: "0x80570006 (NS_ERROR_XPC_CANT_GET_PARAM_IFACE_INFO)" location: "JS frame :: chrome://navigator/content/tabbrowser.xml :: updateTitlebar :: line 759" data: no] SessionStore: [Exception... "Cannot find interface information for parameter arg 0 [nsIDocShell.contentViewer]" nsresult: "0x80570006 (NS_ERROR_XPC_CANT_GET_PARAM_IFACE_INFO)" location: "JS frame :: chrome://global/content/bindings/browser.xml :: get_markupDocumentViewer :: line 0" data: no] ========================= Here is what I get when I try to close the tab (with right click -> close tab): Error: uncaught exception: [Exception... "Cannot find interface information for parameter arg 0 [nsIDocShell.contentViewer]" nsresult: "0x80570006 (NS_ERROR_XPC_CANT_GET_PARAM_IFACE_INFO)" location: "JS frame :: chrome://navigator/content/tabbrowser.xml :: removeTab :: line 1421" data: no]
Sherman: I guess this is still a problem with current nightlies?
Yes, the problem persists in current nightlies on both 10.5 and 10.6 with the same error message in the Error Console.
Flags: blocking-seamonkey2.1a1?
Can you evaluate these items in the Error Console and paste the result? Components.interfaces.nsIDocShell.number Components.interfaces.nsIContentViewer.number
Tested on the following: Build identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.5; en-US; rv:1.9.3a3pre) Gecko/20100303 SeaMonkey/2.1a1pre Build identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.3a3pre) Gecko/20100303 SeaMonkey/2.1a1pre: ------------ Same result for: Components.interfaces.nsIDocShell.number {3adde256-05a9-43a7-a190-f8fe75eecfd6} Components.interfaces.nsIContentViewer.number {e2e5dd7d-8140-4fc5-b2c3-3a3b4f946fc7} Anything else I should poke at? I have Firebug and the Javascript Debugger extensions installed if those can help.
I see the same thing, with Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.3a3pre) Gecko/20100304 SeaMonkey/2.1a1pre
Does this happens all the time for you? The reason I ask is because I can't reproduce this with my trunk debug build (yesterday's source) on 10.5.8, intel.
Seems to be fixed (at least for me) in the latest nightlies.
Works for me with the latest nightly on 10.5 PPC and 10.6 Intel.
OK, thanks. Rocco, as you're the actual reporter here - do you still see this?
Closing as WFM based on the last few comment. Please REOPEN if it's still a problem.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Flags: blocking-seamonkey2.1a1?
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.