Bug 359933

Summary: Quick Open and Outline dropdowns behave unexpectedly.
Product: [Applications] kdevelop Reporter: Francis Herne <mail>
Component: UI: all modesAssignee: kdevelop-bugs-null
Status: CONFIRMED ---    
Severity: minor    
Priority: NOR    
Version First Reported In: 4.90.91   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Bug Depends on: 358492    
Bug Blocks:    

Description Francis Herne 2016-02-29 17:17:46 UTC 
When entering text in a toolbar widget, there's a typical behaviour pattern for completion-list dropdowns:
 - Entries are highlighted when moused-over, and chosen when clicked on.
 - Up/down arrows highlight the previous/next entry in the dropdown. 'Tab' selects the next entry. 'Enter' chooses the highlighted entry.
 - The dropdown is hidden when an entry has been chosen.
 - The dropdown is hidden when clicking anywhere outside it, including in the textbox or on the toolbar.

E.g. Dolphin and KDE filepicker pathname boxes, KDevelop documentation search box, GIMP brush selection, [...].

More generally, this is the expected behaviour for any dropdown on a toolbar item (e.g. KDevelop forward/back/code buttons).

The Quick Open and Outline entry boxes behave very differently:
 - Clicking on the dropdown hides it.
   - Including the scrollbar handle and arrows!
 - Moused-over elements aren't highlighted, nor are they chosen when clicked on (that hides the dropdown...)
 - Clicking on the textbox, the toolbar, or various other UI elements doesn't hide the dropdown. Clicking in the editor panel or inside a toolview does.

Up/down/tab/enter do behave as normal.

Reproducible: Always
Comment 1 Kevin Funk 2016-02-29 19:27:45 UTC 
The hides-on-click issue is being tracked at: https://bugs.kde.org/show_bug.cgi?id=358492 (release blocker).

The rest of these issues here are inconvenient, but no release blockers. Keeping this open.
Comment 2 Justin Zobel 2021-03-09 22:48:46 UTC 
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.