Bug 61012 - using arrow keys in autocompletion, you can't get back to an empty field
Summary: using arrow keys in autocompletion, you can't get back to an empty field
Status: RESOLVED UNMAINTAINED
Alias: None
Product: konqueror
Classification: Applications
Component: khtml (other bugs)
Version First Reported In: unspecified
Platform: openSUSE Linux
: NOR wishlist
Target Milestone: ---
Assignee: Konqueror Bugs
URL:
Keywords:
: 78711 (view as bug list)
Depends on:
Blocks:
 
Reported: 2003-07-09 23:29 UTC by hughjonesd
Modified: 2024-05-06 18:38 UTC (History)
2 users (show)

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 hughjonesd 2003-07-09 23:29:33 UTC
Version:            (using KDE KDE 3.1)
Installed from:    SuSE RPMs

If you have dropdown autocompletion selected, you can use the up and down arrow keys to choose an autocompletion in a form.

However, once you have hit down once, you can't hit "up" to get back to your original, uncompleted form field. Instead you have to delete your completion manually.

I suggest that this is a bug because
* it's unintuitive: if you "go down" to get to something, I think people expect that "going up" will get you back to where you were.
* it makes it awkward to change your mind about an autocompletion.

Tested on 3.1, will test on CVS.

Best wishes,
Dave
Comment 1 Dawit Alemayehu 2003-07-10 06:29:58 UTC
> However, once you have hit down once, you can't hit "up" to get back to your 
> original, uncompleted form field. Instead you have to delete your completion 
> manually.  
 
No you do not. All you have to do is press the Escape key. 
 
> * it makes it awkward to change your mind about an autocompletion.  
 
See above. 
 
> I suggest that this is a bug because  
>  * it's unintuitive: if you "go down" to get to something, I think people expect 
> that "going up" will get you back to where you were.  
 
I guess this is a personal preference or a behavior present in other browsers ?  
 
Regards, 
Dawit A. 
  
 
Comment 2 hughjonesd 2003-07-10 21:14:17 UTC
OK, but I've been using konqueror since 2.0 and never discovered this behaviour
(and even now you've told me, I'll probably forget it). So I would still stand
on the "unintuitive" point. Yes, it's a personal preference. But I don't know
what other browsers do.
Comment 3 Dawit Alemayehu 2004-04-20 19:50:53 UTC
*** Bug 78711 has been marked as a duplicate of this bug. ***
Comment 4 Alexander Potashev 2011-01-31 15:00:34 UTC
Duplicate of bug 81122
Comment 5 Christoph Cullmann 2024-05-06 18:38:20 UTC
Dear user,

KHTML (and KJS) was a long time more or less unmaintained and got removed in KF6.

Please migrate to use a QWebEngine based HTML component.

We will do no further fixes or improvements to the KF5 branches of these components beside important security fixes.

For security issues, please see:

https://kde.org/info/security/

Sorry that we did not fix this issue during the life-time of KHTML.

Greetings
Christoph Cullmann