Bug 438737

Summary: Search field no longer adjacent to panel when panel is located at top of screen.
Product: [Plasma] plasmashell Reporter: Paul <pip.kde>
Component: Application Menu (Kicker) widgetAssignee: Eike Hein <hein>
Status: RESOLVED INTENTIONAL    
Severity: normal CC: guimarcalsilva, nate, plasma-bugs-null
Priority: NOR Keywords: regression
Version First Reported In: 5.22.0   
Target Milestone: 1.0   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Search field location in pre 5.22 version when panel at top of screen.

Description Paul 2021-06-16 13:14:01 UTC
Created attachment 139389 [details]
Search field location in pre 5.22 version when panel at top of screen.

SUMMARY
Prior to the update to 5.22 the "Application Menu 2.0" search field was adjacent to the panel, as shown in attached screenshot.

This is no longer the case, is that intentional behavior?

If so, then an option to place the search field at top or bottom wouldn't go amiss.

STEPS TO REPRODUCE
1. Place panel at top edge of screen.
2. Open Application Menu.
3. Observe placement of Search Field.

OBSERVED RESULT
Search Field is at the bottom of the Application Menu.

EXPECTED RESULT
Search Field adjacent to the Panel. (As was the behavior pre 5.22)

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20210610
KDE Plasma Version: 5.22.0
KDE Frameworks Version: 5.82.0
Qt Version: 5.15.2
Kernel Version: 5.12.9-1-default (64-bit)
Graphics Platform: X11
Processors: 2 × AMD Athlon(tm) 64 X2 Dual Core Processor 5600+
Memory: 3.8 GiB of RAM
Graphics Processor: NV84

ADDITIONAL INFORMATION
Comment 1 guimarcalsilva 2021-06-24 03:57:59 UTC
I can confirm this is happening, but I don't see why that would be a problem. The search field is focused by default when you open the menu, so you can start typing right away.
Comment 2 Paul 2021-06-24 07:46:11 UTC
It's not a "problem" per se - more a case of aesthetics - it simply looks wrong when the application menu is used with a top panel.
Comment 3 Nate Graham 2022-09-21 17:41:48 UTC
Digging a bit, it turns out this was an intentional change. It appears we wanted the layout to remain consistent, as it reduced code complexity and we had gotten some complaints about the dynamic layout before.