Hi Kevin,
There are some complications with this. Firstly, there's an issue of "focus". In a windows app a list box can get "focus" and hence the keystrokes belong to it. However a html table doesn't get focus - and so the keys would be assigned to the buttons.
But if there was more than one set of browse buttons visible on the page, it's not at all clear _which_ browse should be scrolling.
I'll add it to the list though, as there are a couple of queries lately for keyboard control of the pages.
Cheers
Bruce