Bug 493858 - Ctrl+F shortcut doesn't (immediately) activate global search dialog
Summary: Ctrl+F shortcut doesn't (immediately) activate global search dialog
Status: CONFIRMED
Alias: None
Product: kasts
Classification: Applications
Component: general (other bugs)
Version First Reported In: 24.08.1
Platform: Flatpak Linux
: NOR normal
Target Milestone: ---
Assignee: bart
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-09-30 06:02 UTC by whocares.brad
Modified: 2024-10-01 16:44 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description whocares.brad 2024-09-30 06:02:33 UTC
SUMMARY
When clicking on the search bar in the top left, the global search dialog is displayed and its input field is focused. When hitting Ctrl+F, the small search bar is focused without invoking the global search dialog. Text entered into the smaller search bar does nothing, and only after pressing enter is the global search dialog displayed, without any text entered into its smaller counterpart.

STEPS TO REPRODUCE
1. With Kasts open on desktop, press Ctrl+F
2. Type anything into the search bar
3. Press enter

OBSERVED RESULT
Anything entered into the smaller search input is discarded and the global search dialog appears without any content. It behaves normally from this point.

EXPECTED RESULT
Pressing Ctrl+F should immediately display the global search dialog, the same as if the user clicked on the small search bar with the mouse.

SOFTWARE/OS VERSIONS
Kasts: 24.08.1 (Flatpak)
ADDITIONAL INFORMATION
Comment 1 whocares.brad 2024-09-30 06:14:13 UTC
Additionally, it seems like keyboard shortcuts in general don't work properly from the podcast episode details view, although that may deserve its own ticket.
Comment 2 bart 2024-10-01 16:44:51 UTC
I can reproduce.

Strange that it doesn't work anymore (on the first try at least).  This global search component recently got swapped for a newer type of component from Kirigami (add-ons).  I'm guessing the issue might be related to that new component, or the way it's been implemented here.