Bug 472668 - The first section of a settings window is not highlighted on opening
Summary: The first section of a settings window is not highlighted on opening
Status: RESOLVED DUPLICATE of bug 477184
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (other bugs)
Version First Reported In: master
Platform: Neon Linux
: NOR minor
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: qt6
: 475151 (view as bug list)
Depends on:
Blocks:
 
Reported: 2023-07-26 14:11 UTC by Patrick Silva
Modified: 2023-12-03 00:12 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
screenshot (60.19 KB, image/png)
2023-07-26 14:11 UTC, Patrick Silva 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Patrick Silva 2023-07-26 14:11:56 UTC 
Created attachment 160541 [details]
screenshot

STEPS TO REPRODUCE
1. open whatever task manager settings, system tray settings, digital clock settings
2. 
3. 

OBSERVED RESULT
the first section in the left side is not highlighted. The attached screenshot shows the task manager settings.

EXPECTED RESULT
the first section is highlighted on opening

SOFTWARE/OS VERSIONS
Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.27.80
KDE Frameworks Version: 5.240.0
Qt Version: 6.6.0
Graphics Platform: Wayland
Comment 1 Nate Graham 2023-07-26 20:37:10 UTC 
Cannot reproduce. Can you reproduce it, Justin?
Comment 2 Justin Zobel 2023-07-27 02:10:27 UTC 
I can reproduce this. When I open Task Manager Settings there is no highlight, once I click on something it does highlight but it should highlight immediately.
Comment 3 Nate Graham 2023-07-28 20:42:20 UTC 
My mistake, I can indeed reproduce this. I was in Plasma 5 when I was testing it. :facepalm
Comment 4 guimarcalsilva 2023-10-02 20:09:00 UTC 
*** Bug 475151 has been marked as a duplicate of this bug. ***
Comment 5 Patrick Silva 2023-12-03 00:12:31 UTC 

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