After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 143928 - Opening new tab (Ctrl-t) gives focus to gtkmozembed and not the URL-entry field as it should.
Opening new tab (Ctrl-t) gives focus to gtkmozembed and not the URL-entry fie...
Status: RESOLVED DUPLICATE of bug 72125
Product: galeon
Classification: Deprecated
Component: User interface
unspecified
Other Linux
: Normal normal
: ---
Assigned To: galeon-maint
galeon-maint
Depends on:
Blocks:
 
 
Reported: 2004-06-08 07:40 UTC by Mattias Eriksson
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.5/2.6



Description Mattias Eriksson 2004-06-08 07:40:23 UTC
When you type Ctrl-t most users expect the url-field to be focused, galeon
however gives focus to the gtkmozembed. I don't know if this is done
intentionally to use with the "type ahead" (or what they call the type to jump
to a link) thing, or by accident. But since typing in the url-field is one of
the most common tasks when browsing using the keyboard, I think this should be
fixed. 

I first thought this was the bug
http://bugzilla.gnome.org/show_bug.cgi?id=72125, but that seems to only be tabs
in the background. I talk about the active tab (window) taking focus from the
URL-filed.
Comment 1 Crispin Flowerday (not receiving bugmail) 2004-06-08 08:34:37 UTC
This is just another manifestation of bug 72125

*** This bug has been marked as a duplicate of 72125 ***
Comment 2 Mattias Eriksson 2004-06-08 08:40:16 UTC
Well yes I guess the gtkmozembed steal focus problem is the same, the
workarounds for 72125 is specific for tabs in the background. So it might be
possible to workaround bug 72125 without solving this issue, that is why I
posted this as a separate bug. I might thing a dependecy might be ok, but
marking the bug a dupelicate might lead to the bug beeing forgotten if the
workarounds for 72125 gets applied and that bug is closed.