Closed Bug 210952 Opened 21 years ago Closed 15 years ago

failed tab is not closed by Ctrl-F4

Categories

(SeaMonkey :: Tabbed Browser, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: gaemon, Unassigned)

References

()

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4b) Gecko/20030516 Mozilla Firebird/0.6 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4b) Gecko/20030516 Mozilla Firebird/0.6 when downloading a webpage fails, that page is not closed by Ctrl-W or Ctrl-F4 (windows). for example http://www.elby.ch/ is currently (might be available soon) not on DNS. didn't check timed-out pages, but they seems to be too. Reproducible: Always Steps to Reproduce: 1. try opening http://www.elby.ch (provided URL) in background tab, with middle mouse click 2. wait until `cannot find... check the name' dialog pops up. 3. select the `(untitled)' tab. Actual Results: the tab window background is gray, compared to white which you get opening in foreground. try press Ctrl-W or Ctrl-F4 (windows). it doesn't close. of course pressing close tab button works tho. Expected Results: whenever close the tab with keyboard combo. I suggest firebird deals with DNS resolv error as IE does. popup dialogs are somewhat distracting, esp. it is from background job.
Its in DNS now, how about http://www3.thisdomaindoesnotexist.world as an alternate? The error pages (instead of dialog) functionality causes the back button to break, which is why its disabled by default, the devs are working on it.
This behaviour is present on the SeaMonkey trunk as well. It is similar to some comments in 192726, but its not a true duplicate. Not going to confirm this myself as I can't reassign. --> Browser-Tabbed Browser --> NEW
reassigning as per my previous comment
Assignee: blaker → jaggernaut
Status: UNCONFIRMED → NEW
Component: General → Tabbed Browser
Ever confirmed: true
Product: Phoenix → Browser
QA Contact: asa → pmac
Version: unspecified → Trunk
*** Bug 211253 has been marked as a duplicate of this bug. ***
Confirmed with latest Firebird Nightly Mozilla Firebird 0.6 Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5a) Gecko/20030720 Mozilla Firebird/0.6
*** Bug 221723 has been marked as a duplicate of this bug. ***
This seems to be fixed on Seamonkey (just tried on 2003100904). This is broken on Firebird 0.6.1, which is the latest I have, but I would think that if one were to try it on a recent Firebird nightly, it would be found that this problem has been fixed there as well.
On firebird this works using Ctrl-W, but not Ctrl-F4 of course, this is because Ctrl-F4 and Ctrl-W are not the same functionality (F4 closes the current tab only (meaning it won't close your window if its the last tab) and W closes the current tab or the current window (if no other tabs are open) http://lxr.mozilla.org/mozilla/source/toolkit/content/widgets/tabbrowser.xml#1236 is where the Ctrl-F4 lives. If this is fixed in Seamonkey (both Ctrl-F4 and Ctrl-W work on a failed tab) please move this to Firebird and assign to me. Thanks!
Argh... forgot to try Ctrl-F4 (I had been focused on Ctrl-W since the bug I'd just duped was about that exclusively.) Verily, CTRL-F4 doesn't close the tab on Seamonkey either. Adjusting summary accordingly (was: failed tab is not closed by Ctrl-W or Ctrl-F4).
Summary: failed tab is not closed by Ctrl-W or Ctrl-F4 → failed tab is not closed by Ctrl-F4
This bug looks related to bug 110718 (fixed, about event-handers and tabs: "CTRL-T, CTRL-N, and some menus / apps don't work / respond when current tab / page is loading.") and maybe even depends on bug 102831 (if focus is the url bar, ctrl-f4 does not close the topmost tab).
My experience about this bug is that CTRL+F4 has always worked for me (except when the focus is in the URL bar, but that's another bug: bug 102831. I have been using for many months Mozilla 1.6 Final and now I have just downloaded Mozilla 1.7 RC1 (for Win32) and observe this behaviour: If I have some tabs open (with an image on each one), and I hit CTRL+F4, it works. But the second I hit CTRL+F4 it doesn't work. It works again only if I click on the image. I have also notices that with this release the CTRL+Click on a link doesn't open the link on a new tab anymore, now it works opening a new window. Is this a bug? Why can't I find it?
Sorry about the comment of CTRL+CLICK. It was my fault. For any reason my profile lost the correct setting in Edit -> Preferences -> Navigator -> Tabbed Browsing. :( Another bug in the RC1??
Product: Core → SeaMonkey
Assignee: jag → nobody
QA Contact: pmac → tabbed-browser
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
Do anyone know the equivalent bug of this one that targets Firefox instead of Seamonkey?
(In reply to comment #0) > 2. wait until `cannot find... check the name' dialog pops up. > ... > I suggest firebird deals with DNS resolv error as IE does. popup dialogs are > somewhat distracting, esp. it is from background job. Seamonkey 2 has this error page. So INVALID for this one. Bug 137477 has more about not closing tabs.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.