Bug 360085

Summary: Search field gets cleared in mid-typing while on home screen. Can't finish search string (video example included)
Product: [Applications] Discover Reporter: Unknown <null>
Component: discoverAssignee: Aleix Pol <aleixpol>
Status: RESOLVED FIXED    
Severity: normal CC: alex.thierry, null
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Kubuntu   
OS: Linux   
URL: https://youtu.be/fEWxumWPPH0
Latest Commit: http://commits.kde.org/discover/5a9968754e29a4dd758c03aab960fa1e18f53664 Version Fixed In:
Sentry Crash Report:

Description Unknown 2016-03-04 18:11:15 UTC 
See video in URL field for example.

From the home screen, if I select the search field and begin typing the name of the package I want to install, the field is cleared as I'm typing, erasing some of the characters I'd typed before.

Typing in search field from other windows in Discover seems to work fine; it appears to be just the home screen.

Reproducible: Always

Steps to Reproduce:
1. Open Discover.
2. Click or highlight search field from home screen.
3. Begin typing to search for packages.

Actual Results:  
The beginning characters from the search that is typed is erased or cleared, resulting in undesired search results.

Expected Results:  
Search field shouldn't clear characters in mid-typing.

Bug discovered on Kubuntu 15.10 x64 with KDE Plasma 5.5.4 via Kubuntu backports ppa.
Comment 1 Aleix Pol 2016-03-17 15:41:24 UTC 
Git commit 5a9968754e29a4dd758c03aab960fa1e18f53664 by Aleix Pol.
Committed on 17/03/2016 at 15:34.
Pushed by apol into branch 'Plasma/5.6'.

Improve combined search and navigate behaviour

Prevent clearing the search field when navigating into a search.
Navigate up when the search has been cleared.

M  +8    -2    discover/qml/DiscoverWindow.qml
M  +6    -2    discover/qml/Main.qml
M  +9    -1    discover/qml/MuonToolbar.qml

http://commits.kde.org/discover/5a9968754e29a4dd758c03aab960fa1e18f53664
Comment 2 Aleix Pol 2016-04-07 20:20:08 UTC 
*** Bug 361476 has been marked as a duplicate of this bug. ***