Bug 439993 - Elements in a panel jump around when navigating using up/down keys
Summary: Elements in a panel jump around when navigating using up/down keys
Status: RESOLVED DUPLICATE of bug 439459
Alias: None
Product: systemsettings
Classification: Applications
Component: general (show other bugs)
Version: 5.22.3
Platform: Other Other
: NOR minor
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-07-18 07:55 UTC by Vincent
Modified: 2021-08-04 19:34 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Displaced elements (209.16 KB, image/png)
2021-07-18 07:55 UTC, Vincent
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Vincent 2021-07-18 07:55:59 UTC
Created attachment 140152 [details]
Displaced elements

SUMMARY
When you use the arrow keys to select elements in the second panel from the left, the items jump to top or bottom and lose their original position.

STEPS TO REPRODUCE
1. Open System Settings.
2. Click on Shortcuts under Workspace.
3. Click on Custom Shortcuts.
4. Press Down key.

OBSERVED RESULT
The elements jump to the bottom of the panel.

EXPECTED RESULT
The element position should not change.

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.22
KDE Plasma Version: 5.22.3
KDE Frameworks Version: 5.84.0
Qt Version: 5.15.3
Kernel Version: 5.8.0-59-generic (64-bit)
Graphics Platform: X11

ADDITIONAL INFORMATION
Attached a screenshot as proof.
Comment 1 Paul Worrall 2021-07-18 09:32:34 UTC
Reproducible in all systemsettings categories where there are "sub-items", regardless of whether they are displayed in a middle panel or in the left hand panel.

Operating System: KDE neon 5.22
KDE Plasma Version: 5.22.3
KDE Frameworks Version: 5.84.0
Qt Version: 5.15.3
Kernel Version: 5.8.0-59-generic (64-bit)
Graphics Platform: X11
Processors: 2 × AMD A6-6400K APU with Radeon(tm) HD Graphics
Memory: 7.7 GiB of RAM
Graphics Processor: AMD CEDAR
Comment 2 Nate Graham 2021-08-04 19:34:01 UTC
In fact this was just fixed!

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