Closed
Bug 329365
Opened 19 years ago
Closed 19 years ago
can't close tab
Categories
(SeaMonkey :: Tabbed Browser, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 137477
People
(Reporter: eyalroz1, Unassigned)
Details
(Keywords: qawanted)
using sm 2006-03-02. Trying to close my first tab doesn't work, and I get
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 :: removeTab :: line 1028" data: no]
Dupe?
| Reporter | ||
Comment 1•19 years ago
|
||
Oh, using adblock plus 0.6.1.1 and a disabled multizilla.
Keywords: qawanted
Whiteboard: dupeme
dup of bug 137477?
See bug 137477 comment 103, 105, 108.. various extensions seem to trigger this
| Reporter | ||
Comment 3•19 years ago
|
||
I don't have any of the attachments mentioned, there, so I can't know whether it's the same problem or not :-( .
Comment 4•19 years ago
|
||
Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.9a1) Gecko/20060316 Firefox/1.6a1
(In reply to comment #3)
> I don't have any of the attachments mentioned, there, so I can't know whether
> it's the same problem or not :-( .
I may be misunderstanding your terminology, but the key here is that bugs in
extensions are not (as a rule) processed through the Firefox bugzilla.
If you think that you have found a bug in Adblock, please discuss it in the
Adblock forums - there may already be a fix for you.
If you think that this is a bug in Firefox, please be prepared to reproduce
it using a recent nightly and with a fresh profile.
| Reporter | ||
Comment 5•19 years ago
|
||
(In reply to comment #4)
> I may be misunderstanding your terminology, but the key here is that bugs in
> extensions are not (as a rule) processed through the Firefox bugzilla.
It's not a bug with any of the extensions AFAIK. I was just mentioning the fact that I have them installed to better describe my working environment and perhaps allow more people to reproduce the bug.
Comment 6•19 years ago
|
||
Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.9a1) Gecko/20060320 Firefox/1.6a1
If I am not helping, I apologise, and this will be my last comment here. Are you
able to confirm that your bug exists with a fresh profile (no extensions)?
Alternatively, can you give a recipe for reproduction.
I do understand that between us there may be a language barrier, but I don't
see why this should not be considered a dup of Bug 137477 "Some tabs cannot be closed"
| Reporter | ||
Comment 7•19 years ago
|
||
>Are you
> able to confirm that your bug exists with a fresh profile (no extensions)?
> Alternatively, can you give a recipe for reproduction.
No, the bug does not manifest with a new profile. I can't give you a recipe for reproduction, at least for now.
> I don't see why this should not be considered a dup of Bug 137477 "Some tabs
> cannot be closed"
On second reading, I have no idea what the hell I was thinking in my first reply.
*** This bug has been marked as a duplicate of 137477 ***
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
| Assignee | ||
Updated•17 years ago
|
Product: Core → SeaMonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•