Run the following JavaFX application, which uses RichTextFX:
import javafx.application.Application;
import javafx.scene.Scene;
import javafx.scene.control.ScrollPane;
import javafx.stage.Stage;
import org.fxmisc.flowless.VirtualizedScrollPane;
import org.fxmisc.richtext.StyleClassedTextArea;
public class Pagination extends Application {
public static void main( final String[] args ) {
launch( args );
}
@Override
public void start( final Stage stage ) {
final var editor = new StyleClassedTextArea( false );
final var scrollbars = new VirtualizedScrollPane<>( editor );
scrollbars.setVbarPolicy( ScrollPane.ScrollBarPolicy.ALWAYS );
editor.setWrapText( true );
stage.setScene( new Scene(scrollbars) );
stage.show();
}
}

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.The view port navigates back one page for as long as the key is held, or the top is reached.
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:
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.)
I've had look and was able to replicate the problem, but I haven't determined what causes it.
Will have a look next week and see if I can find out why .....
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.