https://bugs.kde.org/show_bug.cgi?id=430326

--- Comment #4 from Kishore Gopalakrishnan <kishor...@gmail.com> ---
(In reply to Alexander Lohnau from comment #3)
> Hey, it seems that there are users who actually utilize this behavior. The
> idea is that they type the query and it gets autocompleted and they just
> press enter.
> 
> This requires the user to know exactly in which order the results will be
> sorted.
> 
> I get that it can be annoying, but then it is more of a duplicate of the
> mentioned bug :)
> 
> *** This bug has been marked as a duplicate of bug 427672 ***

I see. But this sounds quite disruptive. 

I usually know that, for example, 'kinfocenter' appears on top if I type
'kinfo'. Sometimes, I make a typo which returns no results, but press enter
before noticing the typo and the lack of results. Let us say I typed 'kindo'
and pressed enter. Nothing happens at that moment, which is perfectly fine.
Now, I Press ctrl+backspace (to clear the query), and then start trying to type
the correct query ('kinfo'). But, when I type 'ki', 'Kile' appears as the first
result and gets selected before I can even finish typing what I mean to type. 

In fact, this behaviour persists even if I dismiss krunner (press 'esc') and
invoke it again. For example,
1. Invoke krunner
2. Press 'enter'
3. Dismiss krunner
4. Invoke krunner
5. Type anything that returns a result
leads to the IMO unexpected behaviour of running something after step 5, even
if the user has not pressed 'enter'. This was actually how I noticed this
behaviour in the first place, but I settled on the steps in comment #0 as an
apparently simpler way to demonstrate the behaviour. Is it intentional that
this 'runAutomatically' persists even after the user has dismissed krunner?

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to