I have run into this issue as well. In the end I handle keyboard
events myself (but I also needed jumping to items as the user is
typing their names).
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To post to this group, send email to goo
I have had no feedback on this but I think it is a serious but fairly
easily resolved problem so I have reported it as an issue -
http://code.google.com/p/google-web-toolkit/issues/detail?id=6777
On Aug 16, 4:40 pm, camerojo wrote:
> Cell widgets were a great step forward for GWT - enabling effic
Whoops - ignore the last two lines below - they snuck into my posting
by mistake...
> I suggest either redefining, creating a new enum, or allowing
> pluggable policies
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To post to this group
Cell widgets were a great step forward for GWT - enabling efficient
client display of very large amounts of server data by means of
RangeChangeEvents processed by AsyncDataProviders.
However there is a serious problem with keyboard navigation as defined
by KeyboardPagingPolicy.INCREASE_RANGE.
Sup
