172398 - blank window tab will not close with control W

Status: RESOLVED DUPLICATE of bug 140119

(SeaMonkey :: General, defect)

Description

[david schwartz]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.0.0) Gecko/20020529
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.0.0) Gecko/20020529

i click on a link to open in a new tab.  the page does not load. tab says
untitled and url says  about:blank

tab is in blue  i click on control W to close and tab will not close

putting the cursor on the tab and holding down the button reveal a drop down
with close tab, i chose that and the blank tab will close

Reproducible: Always

Steps to Reproduce:
1.i have set new window to open as new tabs
2.command click on link open new location
3.window wont load so i click control w  (tab is blue or active)

Actual Results:  
tab does not close

Expected Results:  
should have closed tab

Comment 1

[Greg K.]

david, 1.0 is too old for bug reporting. Please retest with a more recent build.

Comment 2

[Rack]

I know for a fact that 1.1 also acted similarly, and the Phoenix nightly cvs is
acting the same way.  Pages which are 'blank' due to, say, a refused connection.

Comment 3

[Rack]

Hmm.. while I'm here, control-tab for tabbed browsing to switch to the next tab,
does not appear to work on pages like this.  I'm guessing it's a related bug.

Comment 4

[Rack]

Pardon the repeat posts.. I just noticed that in some cases, clicking on the
main part of the pane will allow one to ctrl-w with success.

Using a mouse-gesture, I had a new window pop up and attempted a ctrl-w.  I
wasn't able to do so until I clicked the blank page.

Comment 5

[Damian Yerrick]

Related to bug 140119 ?

Comment 6

[Yuri]

This bug has been there since the beginning of time.  (At least, every single
version of mozilla that i used - going back to 0.7 or so - had this problem. 
This would be for both Linux and Windows versions.)

It's rather annoying, though not critical.

Comment 7

[Andrew Hagen]

Dupe.

*** This bug has been marked as a duplicate of 140119 ***