Wt

WTableView calculations for the selected row and row height and so on seem to be messed up by using the browser in a zoom other than 100%. This causes very serious problems, like when a row is double-clicked, quite often a different row is the row that is activated, and this can go unnoticed. This also has an effect on the "Loading" graphic, where the rows that are visible are calculated incorrectly and the loading graphic is never replaced by the real records.

To reproduce, simply go here: http://www.webtoolkit.eu/widgets/trees-tables/mvc-table-views and change the browser zoom and then start scrolling the WTableView, and then scroll the table under the heading "Virtual scrolling".