Bug 385508 - Mouse interaction with dashboard results in dashboard not navigable from the arrow keys
Summary: Mouse interaction with dashboard results in dashboard not navigable from the ...
Status: RESOLVED DUPLICATE of bug 381879
Alias: None
Product: plasmashell
Classification: Plasma
Component: Desktop Dashboard (show other bugs)
Version: 5.10.5
Platform: unspecified Linux
: NOR normal
Target Milestone: 1.0
Assignee: Marco Martin
URL: https://github.com/Plasmoner/The-thin...
Keywords:
Depends on:
Blocks:
 
Reported: 2017-10-09 08:54 UTC by Richard Addison
Modified: 2020-01-13 03:31 UTC (History)
1 user (show)

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

Attachments
The frame won't move to the next icon when I hold down the key (921.46 KB, text/plain)
2017-10-09 08:54 UTC, Richard Addison 		Details
The frame won't move to the next icon when I hold down the key (921.46 KB, image/jpeg)
2017-10-09 11:08 UTC, Richard Addison 		Details
Show Obsolete (1) View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Richard Addison 2017-10-09 08:54:23 UTC 
Created attachment 108238 [details]
The frame won't move to the next icon when I hold down the key

Action: I click with the mouse on an icon in the dashboard
Result: dashboard impossible to navigate from the arrow keys
Occurrence: every single time
Persistence: temporary
Action to make dashboard key-navigable again: position pointer onto Recent Applications
Avoidable: Yes, if I never use the mouse to interact with the dashboard and use the keys exclusively
Occurrence in plasma 5.8.7: never
Occurrence in plasma series 5.9: never
Present in any distribution featuring plasma version 5.10.5
https://github.com/Plasmoner/The-thing/issues/1

Kind Regards
Comment 1 Richard Addison 2017-10-09 11:08:23 UTC 
Created attachment 108239 [details]
The frame won't move to the next icon when I hold down the key

Sorry for messing up previous attachment
Comment 3 Christoph Feck 2017-10-18 12:38:42 UTC 
Is this a different issue compared to bug 381879?
Comment 4 Nate Graham 2020-01-13 03:31:02 UTC 
Looks like the same issue, yeah.

That got closed and the issue isn't present for me when I try it.

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