Closed Bug 232708 Opened 21 years ago Closed 21 years ago

Ctrl+F4 does not close tab when address bar has focus

Categories

(Firefox :: General, defect, P4)

defect

Tracking

()

RESOLVED FIXED

People

(Reporter: histed237, Assigned: bugzilla)

References

Details

(Keywords: fixed-aviary1.0)

User-Agent: Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031225 Firebird/0.7 If you single click on the URL bar to focus it, then press either Ctrl-W or Ctrl-F4, the currently selected tab should close. Reproducible: Always Steps to Reproduce: 1. 2. 3. Actual Results: Ctrl-W unhighlights the urlbar text and moves the pointer to the front. Ctrl-F4 does nothing. Expected Results: Close the currently selected (but unfocused) tab.
The Ctrl+W problem is Linux-specific and is bug 223675. I'm changing this bug to only cover Ctrl+F4. See also bug 232770, "Tab-switching shortcuts don't work when address bar has focus (Ctrl+Tab, Ctrl+PgDn)".
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Linux → All
Hardware: PC → All
Summary: single-click on url bar then Ctrl-W or Ctrl-F4 does not close current tab → Ctrl+F4 does not close tab when address bar has focus
The same happens when a form text entry field on the current page has the focus... ctrl-w will fail to close the tab.
martin: that's bug 223675, not this bug.
*** Bug 238967 has been marked as a duplicate of this bug. ***
IMHO the bug most probably appears because the GTK+ toolkit defines CTRL-W as 'delete backward word' in text entries (after Emacs). This explains why Windows versions of the browsers does not exhibit this behaviour. See http://www.gtk.org/tutorial1.2/gtk_tut-14.html#ss14.3 Though this is for GTK+ 1.2, I guess the same stands for GTK+ 2.0 too. I don't know, though, if it's possible to override the built in shortcuts in the GTK+.
Saulius: that's bug 223675, not this bug.
This behaviour is not restricted to Firefox. Mozilla has the same behaviour. Duping this bug to 102831 *** This bug has been marked as a duplicate of 102831 ***
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
*** Bug 241004 has been marked as a duplicate of this bug. ***
v
Status: RESOLVED → VERIFIED
Seamonkey has the same bug, but fixing this in Seamonkey would probably not fix it in Firefox.
Status: VERIFIED → REOPENED
Resolution: DUPLICATE → ---
*** Bug 251600 has been marked as a duplicate of this bug. ***
*** Bug 246906 has been marked as a duplicate of this bug. ***
Flags: blocking-aviary1.0?
Flags: blocking-aviary1.0? → blocking-aviary1.0+
Priority: -- → P4
Fixed on branch. I have my own way of tracking bug fixes that need to be imported to the trunk, and that will happen this weekend. Thus, I'm marking this fixed.
Status: REOPENED → RESOLVED
Closed: 21 years ago21 years ago
Resolution: --- → FIXED
Keywords: fixed-aviary1.0
You need to log in before you can comment on or make changes to this bug.