Lost focus during 'open task view' function
See original GitHub issueIn version 991 of the Todoist web application, when I use keyboard shortcut i
to open the task view, the focus appears to be on the parent task element within the UI (blue square in screenshot). This means that none of the context-specific keyboard shortcuts work (e.g. s
, c
, h
).
I am using Google Chrome 80.0.3987.149 on PC
Thanks for your time.
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (5 by maintainers)
Top Results From Across the Web
Make it easier to focus on tasks - Microsoft Support
Focus assist settings can be edited by selecting Start > Settings > System > Focus assist. Or you can type Focus assist into...
Read more >What is Task View in Windows 10 and how to use it
Click or tap on it to open Task View. If the button is missing, right-click or press-and-hold on the taskbar to bring out...
Read more >Why You Can't Focus And How to Stop Losing Focus - Lifehack
Can't focus? Here's the reason why and 19 things you can do to stop losing focus. Learn how to regain focus now.
Read more >4 reasons you can't focus at work (and how to destroy each one)
Learn why you can't focus at work, and what you can do to concentrate and get more done. Don't miss this expert advice...
Read more >Set up a Focus on Mac - Apple Support
Choose Apple menu > System Settings, click Focus in the sidebar, click a Focus, then click the Focus Filter you want to change....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This was tricky, I believe I’ve fixed it! The fix is included in version 77.
The unsatisfying part is that I’m still not sure exactly what was going on, just that it was fiddlyness in the keyboard handling. The satisfying part is that the dispatch for the keyboard input handling is now a lot more sensible.
You’re welcome! Thanks for showing your appreciation 😃
On Mon, Apr 6, 2020 at 1:47 PM thenobody14 notifications@github.com wrote: