Bug 78711 - Konqueror Location-Bar Entry Completion Backtracking Impossible
Summary: Konqueror Location-Bar Entry Completion Backtracking Impossible
Status: RESOLVED DUPLICATE of bug 61012
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Slackware Linux
: NOR wishlist
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-03-30 02:48 UTC by jamethknorth
Modified: 2004-04-20 19:50 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description jamethknorth 2004-03-30 02:48:34 UTC
Version:            (using KDE KDE 3.2.0)
Installed from:    Slackware Packages

If an entry is started (ie: bugs.kde) and a list of options appears in the combo-box (ie: bugs.kde.org/wizard.cgi) and the user moves to the option, the user cannot backtrack.

That is, if I type 'bugs.kde' and then press down, it will give me 'bugs.kde.org/wizard.cgi' (lets assume, for argument sake that is the only site I've been to). Now, if I press up again, nothing happens. In fact, the only way to remove the auto-completion is to manually edit it back out. This is even worse if the option extended from something like ~/videos to 'http://~/videos' because the system tried to make it an internet address, as I would then need to remove from the beginning and the re-adjust to the top.

To solve this, the top entry should always be what was manually typed by the user and the second entry (the first in the combo that is dropped down) should be the most likely match. Then, if a user presses down, pressing up will get them back where they were, which is much more logical than the current situation.

The first entry (what is user typed) would probably have to change if the user next typed. If there another way to do it, that would be nice, but it does not seem possible to get around.
Comment 1 Dawit Alemayehu 2004-03-31 10:58:56 UTC
On Monday 29 March 2004 19:48, jamethknorth@hotmail.com wrote:
> ------- You are receiving this mail because: -------
> You are the assignee for the bug, or are watching the assignee.
>
> http://bugs.kde.org/show_bug.cgi?id=78711
>            Summary: Konqueror Location-Bar Entry Completion Backtracking
>                     Impossible
>            Product: konqueror
>            Version: unspecified
>           Platform: Slackware Packages
>         OS/Version: Linux
>             Status: UNCONFIRMED
>           Severity: normal
>           Priority: NOR
>          Component: general
>         AssignedTo: konq-bugs kde org
>         ReportedBy: jamethknorth hotmail com
>
>
> Version:            (using KDE KDE 3.2.0)
> Installed from:    Slackware Packages
>
> If an entry is started (ie: bugs.kde) and a list of options appears in the
> combo-box (ie: bugs.kde.org/wizard.cgi) and the user moves to the option,
> the user cannot backtrack.
>
> That is, if I type 'bugs.kde' and then press down, it will give me
> 'bugs.kde.org/wizard.cgi' (lets assume, for argument sake that is the only
> site I've been to). Now, if I press up again, nothing happens. In fact, the
> only way to remove the auto-completion is to manually edit it back out.

No you do not. Use the ESC key to cancel completion....

Comment 2 jamethknorth 2004-03-31 14:21:25 UTC
The escape key also stops the current action, so that is not nearly an acceptable solution. It makes the key too multi-purpose and it makes it impossible to edit the line while other things are occuring (yes, I do have situations where I want to do that)

The instinctive things is that, if you pressed down to get a completion, you press up to go back to where you were, so that is how it should function.
Comment 3 Dawit Alemayehu 2004-04-01 08:01:00 UTC
> The escape key also stops the current action, so that is not nearly an
> acceptable solution.

Well that is a matter of preference/opinion. 

> It makes the key too multi-purpose 

Nope. Actually the use of the ESC is consistent in our case because ESC usually means cancel/stop the action which in this case is the listing of the completion items. But that is another matter.

> and it makes it impossible to edit the line while other things are occuring
> (yes, I do have situations where I want to do that)

Uh ? If the completion box is visible and you press the ESC key, that event is consumed by the completion box. And yes that means you can get out of the completion box by pressing the ESC key while a page is still loading. Oh BTW "saying I do have situations..." is worthless since I cannot evaluate whether it is warranted to change the current behavior...

> The instinctive things is that, if you pressed down to get a completion, you
> press up to go back to where you were, so that is how it should function.

Again this is a personal preference or at worst a learned behavior. And as such this is not a bug but rather a wishlist for a change unless you can give an example where the current behavior interferes with other functionality...



Comment 4 jamethknorth 2004-04-01 18:46:53 UTC
> > It makes the key too multi-purpose
>
> Nope. Actually the use of the ESC is consistent in our case because ESC
> usually means cancel/stop the action which in this case is the listing of
> the completion items. But that is another matter. 

Nope, actually the use of the ESC key is consistent to stop or cancel something, but this case isn't canceling or stopping anything, as far as feedback is concerned. The completion is finished, so the ESC key is undoing.

> > The instinctive things is that, if you pressed down to get a completion, you
> > press up to go back to where you were, so that is how it should function. 
>
> Again this is a personal preference or at worst a learned behavior. And as
> such this is not a bug but rather a wishlist for a change unless you can
> give an example where the current behavior interferes with other
> functionality... 
 
It's not just a personal preference. The natural behavior to reverse an action is to do the opposite. Pressing down completes the text, pressing up is the immediate reversal. This is a basic human thought method for most everything.

And the current behavior is a bug from a usability standpoint. And do not tell me again that this is just a case of personal preference. The current system is not the instinctive way most humans reverse actions.
Comment 5 Dawit Alemayehu 2004-04-20 19:50:52 UTC

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