I agree. The current GWT pagination seems to be more of a workaround. They try to avoid having less items on the last page because it might change the layout and the pager position.
What should actually happen is that the table should maintain the full height as if it has all the rows, but display only the few remaining rows on the last page. Basically, the table should have the same height regardless of the number of rows and the pager component should remain in place when switching pages. I'm surprised there isn't an actual bugreport for this. --emi On Dec 21 2011, 3:16 am, Steve <stephen...@google.com> wrote: > This behavior deviates from widespread usage of pagination across the web > so I don't see how it's desirable to do something unexpected by users > unless it's clearly superior. > > When I navigate from one page to another it's because I want to see the > next set of results/data and I expect the stuff at the top to be different > than what was on the previous page I was on. If it overlaps, then I have to > scan down and figure out where to start looking. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
