Bug 395432 - In sidebar view, clicking a search result should show the result with the relevant subcategories displayed as well
Summary: In sidebar view, clicking a search result should show the result with the rel...
Status: RESOLVED DUPLICATE of bug 400303
Alias: None
Product: systemsettings
Classification: Applications
Component: sidebarview (show other bugs)
Version: 5.13.0
Platform: Arch Linux Linux
: NOR minor
Target Milestone: ---
Assignee: Marco Martin
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-06-15 14:40 UTC by Kishore Gopalakrishnan
Modified: 2019-07-25 13:31 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Display when we navigate to the 'mouse' KCM through search (51.60 KB, image/png)
2018-06-15 14:40 UTC, Kishore Gopalakrishnan
Details
Display when we navigate to the 'mouse' KCM by clicking the subcategories (73.38 KB, image/png)
2018-06-15 14:42 UTC, Kishore Gopalakrishnan
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Kishore Gopalakrishnan 2018-06-15 14:40:05 UTC
Created attachment 113350 [details]
Display when we navigate to the 'mouse' KCM through search

If I search for an item in the search bar in the 'system settings' application, I can click on one of the results to go to the relevant KCM. However, doing this does not show the 'complete' sidebar view (i.e. the information on which category the KCM belongs to is missing), which is a bit disorienting.

Ideally, the sidebar would be completely expanded even if we have navigated to the KCM by using the search bar.
Comment 1 Kishore Gopalakrishnan 2018-06-15 14:42:25 UTC
Created attachment 113351 [details]
Display when we navigate to the 'mouse' KCM by clicking the subcategories

What I meant to say in the previous comment is that the second sidebar visible in the above screenshot should have also been visible when we directly search for 'mouse' in the system settings search bar and click on the result.
Comment 2 Nate Graham 2019-07-25 13:31:31 UTC

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