[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-bugs-dist
Subject: [Bug 89385] New: find-as-you-type shouldn't block key events after
From: MaxAuthority <stubenschrott () gmx ! net>
Date: 2004-09-12 22:21:36
Message-ID: 20040913002133.89385.stubenschrott () gmx ! net
[Download RAW message or body]
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
http://bugs.kde.org/show_bug.cgi?id=89385
Summary: find-as-you-type shouldn't block key events after
following a link with <return>.
Product: konqueror
Version: 3.3
Platform: unspecified
OS/Version: Linux
Status: UNCONFIRMED
Severity: wishlist
Priority: NOR
Component: khtml
AssignedTo: konq-bugs kde org
ReportedBy: stubenschrott gmx net
Version: 3.3 (using KDE 3.3.89 (CVS >= 20040820), Gentoo)
Compiler: gcc version 3.3.3 20040412 (Gentoo Linux 3.3.3-r6, ssp-3.3.2-2, \
pie-8.7.6)
OS: Linux (i686) release 2.6.8-rc2
I think, if a link with type-ahead-find is found and (Ctrl-)Enter is pressed, the \
timeout for blocking the keyboard globally should end.
Since when I browse some forums with the keyboard, I usually search for a link, and \
open it with Ctrl-Enter in the background, than it would be convenient to immediately \
being able to search for the next link by pressing ', instead of waiting up to 3 \
seconds or having to hit 'Esc' before searching for a new string.
This changed a little bit to the better in newer CVS version, so at least, when \
opening a link in the current tab/window, when the new site is loaded the keyboard \
block is disabled. But sometimes, you have a slow internet connection, and so the new \
site doesn't load immediately, so the block should be released IMMEDIATELY after \
pressing (Ctrl-)Enter to follow a link.
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic