[GH-ISSUE #580] List PgDn / PgUp semantics are inverted when hitting the list item boundary conditions #424

New issue

Closed

opened 2026-03-04 01:04:52 +03:00 by kerem · 1 comment

kerem commented

2026-03-04 01:04:52 +03:00

Owner

Originally created by @berrange on GitHub (Mar 15, 2021).
Original GitHub issue: https://github.com/rivo/tview/issues/580

When there are further items off screen, PgDn will move down to select the next set of items, but when there are no further items, PgDn will do the inverse and select the first item, instead of selecting the last item.

Similarly, when there are previous items off screen, PgUp will move up to select the previous set of items, but when there are no further items, PgUp will do the inverse and select the last item, instead of selecting the first item

This gets particularly confusing in the common case where all items fit on the screen - PgDn always selects the first item, while PgUp always selects the last item - which is opposite of what people are expecting.

Originally created by @berrange on GitHub (Mar 15, 2021). Original GitHub issue: https://github.com/rivo/tview/issues/580 When there are further items off screen, PgDn will move down to select the next set of items, but when there are no further items, PgDn will do the inverse and select the first item, instead of selecting the last item. Similarly, when there are previous items off screen, PgUp will move up to select the previous set of items, but when there are no further items, PgUp will do the inverse and select the last item, instead of selecting the first item This gets particularly confusing in the common case where all items fit on the screen - PgDn always selects the first item, while PgUp always selects the last item - which is opposite of what people are expecting.