I completely understand your logic here but the fact it's not working makes it additional functionality 
I tried to hack around it mainly by trying to subscribe to the selectedRowIndex and calculate when a page should change. If the table holds n = 10 rows, each n+1 row is outside the current view and would trigger a selectPage(selectedPageIndex + 1) call to the table. Dirty, but should do the job.
Didn't have much luck, which made me also realise that this is a mini feature improvement to basically Treat arrowing down/up a table as a Row Select event which you could then use to turn pages.
Other then that, you could add a feature request :))