(*** This bug was imported into bugs.kde.org ***) Package: kdelibs Version: 2.1 Beta 2 Severity: normal Installed from: source If you enter an URL very fast in the keyboard I believe there must not be direct focus in it(don't click in the url location widget start a new konqui!) sometimes you enter an URL and when you hit enter not the URL is loaded rather an extra space is appended. (submitted via bugs.kde.org)
mmh@gmx.net wrote: > > Package: kdelibs > Version: 2.1 Beta 2 > Severity: normal > Installed from: source > > If you enter an URL very fast in the keyboard I believe > there must not be direct focus in it(don't click in the > url location widget start a new konqui!) sometimes you > enter an URL and when you hit enter not the URL is > loaded rather an extra space is appended. > I can't reproduce this at all. If the location field has no focus you can't type URLs. No mater how fast. And when I press Enter everything works as expected no mater how fast I tried to write. Do you have any debug output that shows what goes wrong? With this I can't handle it and would close it ;( Greetings Stephan -- It's my true belief that people having wishes for the bug report tool and report it to the author haven't got the idea behind open source. anonymous KDE developer
--VbJkn9YxBvnuCH5J Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi I really thinkg the focus is the problem of this bug. Another symptom of this bug is that if you set konqui to popup completeion it is completely broken in a newly started konqui if you do NOT click in the location bar before you type. The completion popup comes up but disappears again immediately. (flickers) --=20 Moritz Moeller-Herrmann mmh@gmx.net ICQ# 3585990 Mosh: =BBMoritz ist ein weltbekannter Troll=AB --VbJkn9YxBvnuCH5J Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.3 (GNU/Linux) Comment: Weitere Infos: siehe http://www.gnupg.org iD8DBQE6cye7zPDJgxvnSxERAqE2AJ988c/Ysa7NS4pm1EjtALQxaGUNcwCghveQ eP/ZONsaOCHrAiV1hUoxHeE= =Il/b -----END PGP SIGNATURE----- --VbJkn9YxBvnuCH5J--
Hi! I'm still failing to understand what you're doing. When I start konqueror the location bar has no focus so I can't type without giving focus to it. So what are you doing _exactly_? Greetings Stephan -- It's my true belief that people having wishes for the bug report tool and report it to the author haven't got the idea behind open source. anonymous KDE developer
--AhhlLboLdkugWU4S Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri Feb 02 2001 at 10:54:45PM +0100 Stephan Kulow wrote: > Hi! >=20 > I'm still failing to understand what you're doing. When I start > konqueror the location bar has no focus so I can't type without > giving focus to it. So what are you doing _exactly_? Well I recompiled yesterday and the bug persists. I have focus follows mouse I start konqueror by clicking on on a button on kicker (not k-menu). I then move the mouse over the konqueror AHH I just noticed you must not put focus on any other window. If focus is on another window first you can't type. If you move the mouse directly from kicker to konqueror you CAN type with all the effects I described. --=20 Moritz Moeller-Herrmann mmh@gmx.net ICQ# 3585990 Mosh: =BBMoritz ist ein weltbekannter Troll=AB --AhhlLboLdkugWU4S Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.3 (GNU/Linux) Comment: Weitere Infos: siehe http://www.gnupg.org iD8DBQE6e1THzPDJgxvnSxERAjPxAJ4xDcHBQ+0IZjC3PsSUEuNXapvGYACfS1nY t9XfFq2NZviUN83pprePEls= =qpOx -----END PGP SIGNATURE----- --AhhlLboLdkugWU4S--
I've seen this also - since there was some confusion about the symptoms and what causes them I'll share my experience: When entering text in the "Location" field (or in certain other one-line fields) if you type quickly enough the <return> and <tab> keys won't work properly. Rather than acting like an <end-of-input> or <enter> function the <return> is interpreted as a space or other non-visible character. Rather than acting like a <jump-to-next-field> function the <tab> is also interpreted in this way.
I have not noticed the behavior anymore since QT-2.3 and KDE-2.2a1 has anyone else still seen this? -- Moritz Moeller-Herrmann ICQ #3585990
It is still presetnm but hard to trigger. You have to start a new browser window to see it so I guess it is an initialisation issue. Then type something fast and hit ENTER immediately you will get a space in the place of the ENTER. -- Moritz Moeller-Herrmann mmh@gmx.net ICQ# 3585990 Mosh: »Moritz ist ein weltbekannter Troll«
Hi I just wanted to say that in my current CVS KDE the problem still persists. Whenever I enter text in a textfield (not only the location bar but also forms in a webpage) very fast and hit enter sometimes the enter gets replaced by a space character. Just my 2c. Jelmer Feenstra