-
Notifications
You must be signed in to change notification settings - Fork 167
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Keyboard shortcuts sometimes don't work #1197
Comments
I can confirm this. And I would say that not sometimes, but quite often. |
Currently I am running the latest version from Git and I am trying to read the following book:
|
Thank you for reporting this. Could you please specify your operating system (Windows, Linux or MacOS). Could you also indicate whether or not you are using Thorium with a screen reader (and if so, which one). Most importantly, which version of Thorium are you using? (on GitHub there are the official "stable" releases, and the "nightly" automated builds) |
Windows 10, version 2004 |
Okay thank you. The |
Oh sorry. I tested against develop branch. |
I've found a reproducible case. Open a document in full screen, accidentally hit ctrl-s, the arrow keys no longer work. You have to leave full screen (why doesn't esc work for this?) and realize you have If there are modalities in the interface you need visual feedback indicating them and The only documentation for the keyboard functions I find is the settings panel from Thorium renders documents beautifully. With a better interface and documentation it |
Great report, thank you. |
However that's not always the case. Sometimes they don't work, you insist and then they do work. Happened on stable, happens also on Nightly. Windows 10, NVDA screen reader. |
Comment from NNELS (Danny Faris @BCLibCoop ):
|
I reproduce the error with NVDA and windows 10 : when on fullscreen |
Using |
I cannot provide steps to reproduce as it doesn't always happen, but specifically ctrl+pgup and ctrl+pgdn sometimes don't jump to next and previous chapters.
The text was updated successfully, but these errors were encountered: