Bug 73248 - Text entry focus problems
Summary: Text entry focus problems
Status: RESOLVED DUPLICATE of bug 66296
Alias: None
Product: kdelibs
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Stephan Kulow
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-01-22 16:55 UTC by Dennis Noordsij
Modified: 2004-01-22 17:22 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dennis Noordsij 2004-01-22 16:55:43 UTC
Version:            (using KDE 3.2.0 RC1, compiled sources)
Compiler:          gcc version 3.3.2 (Debian)
OS:          Linux (i686) release 2.6.0

To try:

Open up Konqueror
Go to http://www.google.com
Type something into the text entry box (do not hit enter or click search)
Click somewhere else on the page to make the entry lose focus (just background, no widgets)
Doubleclick the entry to highlight the contents
Type something ... it will not go to the entry box (i.e. nothing will happen :-)

(Similar, just start Konqueror, type in http://www.google.com [enter], the text entry caret is blinking to indicate the entry box has focus, yet if you type nothing happens, you have to click in the entry box to really set the focus).

Bites me all the time, introduced as far as I can tell in beta2, now in rc1. Never noticed it in 3.1.[45] (Debian).
Comment 1 Dennis Noordsij 2004-01-22 16:59:32 UTC
The second example only happens when I start Konqueror from Kicker, if it's been running for a while it might work.

When you doubleclick the entry box to select the text, at the first click the clipboard icons will undim to suggest the entry has focus (and if you click only once then everything works), and the second click will dim the icons to suggest it has lost focus. (which it shouldn't have of course).
Comment 2 Stephan Binner 2004-01-22 17:22:28 UTC

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