>> - Page Up/Down: go up/down by n elements (bounded by first/last), where n is >> the size of the current page (for example in a List or a Table with size 20 >> elements the page here could be 20) ... > > Not sure this makes sense. Page up/down is currently handled by ScrollPane, > which, in most cases, will be used to host a list, table, or tree. So I think > the current behavior is probably OK. We could certainly revisit this later, > though.
Might it make sense to have TextArea override scrollToVisible() to also update the position of the caret? Though as I think about it, I'm not sure that would come into play here anyway...
