There's an obvious workaround:
@table.setCurrentItem(0,0)
in initialize. But it seems to me that a minimal table defininition
should not be able to generate exceptions. This is also a rather hard
exception to catch usefully, since it happens in internal keyboard handling.