GNOME Bugzilla – Bug 117240
gnome-terminal/tabs/focus
Last modified: 2006-04-29 00:02:58 UTC
if you use tabs in gnome-terminal and click on the tab it will focus the title of the tab, with wich you can't do anything. it should give the focus to the terminal. so that you can use it right away, without clicking into it first. this ony happens if you click on the active tab; or double click one. other applications using tabs, like epiphany, give the focus to the window as soon as you do something (in this case hitting up/down keys)
epiphany (and every other tab in every other app ;-)) works the same way for me. if this is changed it should be changed in gtk. I believe I tested on Windows XP a while back and it also worked the same way. You need to be able to focus tabs, for keyboard navigation, and standardly clicking a focusable widget focuses that widget. Tabs have the exception that clicking them while they are inactive doesn't focus them, but you can still focus the active tab. Just don't double click the tabs. ;-) Anyhow, a gtk request if anything. Nothing special about the terminal in this area.
(I'm coming to this from Redhat bug #149327 which is the same bug as this, I believe). - tabs in firefox don't have this behavior (I'm just providing a counter example to "every other app"). - the main text area in epiphany doesn't need focus in the same way that a terminal does (no character input is the difference I think?). - Even if the tabs accept focus, they should relinquish it in focus-follows-mouse mode. - Gnome-terminal tabs take focus from click-drag, not just double-click. - Its a bug because it surprises the user when the mouse is over the terminal window and characters are not accepted. I'll try reporting this against Gtk
Reported against Gtk2: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=153221
*** Bug 145302 has been marked as a duplicate of this bug. ***
*** Bug 319317 has been marked as a duplicate of this bug. ***
*** Bug 320411 has been marked as a duplicate of this bug. ***
*** Bug 340051 has been marked as a duplicate of this bug. ***