-
Notifications
You must be signed in to change notification settings - Fork 237
Keyboard paging computation error while paging up #935
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
Comments
I've had look and was able to replicate the problem, but I haven't determined what causes it. |
So this problem seems to be in Flowless, which doesn't have a maintainer at the moment. I've applied and will investigate further, hopefully next week ..... |
Any movement on this @Jugen ? |
Sorry, I did have a look but haven't gotten round to trying to fix it. To be honest it seems complicated/obscure and I've got other priorities at the moment so it's going to be a while I think ..... |
Flowless issue. |
@davejarvis thanks for reporting. I submitted a PR in Flowless that hopefully resolves this. |
Replicate
Ctrl+Home
to navigate to the top of the document.Ctrl+End
to navigate to the bottom of the document.Page Up
to navigate upwards.Expected Results
The view port navigates back one page for as long as the key is held, or the top is reached.
Actual Results
The computation for the new caret position goes awry in a variety of ways, depending on how much text is pasted and the view port size, resulting in one of the following behaviours:
Bonus "Bug"
Possibly considered a feature request, most word processors allow the page up key to move the cursor to the top of the document. If there is insufficient room for a complete page before reaching the top of the document (i.e., paragraph 1, care position 1), RichTextFX prevents further paging up. This is atypical behaviour, but not really a bug because it is likely performing to specification. The specification is inconsistent with most other editors. (Compare with the page up/page down behaviour of the text area for writing issues on GitHub, for example.)
The text was updated successfully, but these errors were encountered: