Wt

WTableView doesn't render all rows in the following scenarios tested with the attached application which has 2 tabs with a WCheckBox and a WTableView in each tab. WCheckBox is used to change the row count of the WTableView.

Scenario 1:

• Use Bootstrap theme version 2
• Disable progressive bootstrap
• Show small number of rows at application creation, e.g. 10
• enableUpdates(true)
• Increase row count to, e.g., 100
• Tableviews in both of the tabs in the attached test application fail to render all rows

Scenario 2:

• Use Bootstrap theme version 2
• Disable progressive bootstrap
• Show small number of rows at application creation, e.g. 10
• Don't enable updates
• Increase row count to, e.g., 100
• Tableview only in the lazily loaded second tab in the attached test application fails to render all rows
• Tableview in the default tab renders all rows

See the attached screenshot for an incomplete tableview. Toggle the check box in the attached test application to reproduce the issue.

Some observations:

• Issue occurs if Bootstrap theme v2 is used, v3 and default theme are OK.
• Issue doesn't occur if the initial row count is large. Reducing the row count (e.g. from 100 to 10) and then increasing (back to 100) is OK. So initial row count seems important.
• Issue occurs in the default tab if enableUpdates(true). Lazily loaded tab is always broken regardless of enableUpdates(). So tab loading scheme seems to matter.
• Attached test applicaton recreates the UI after 10 seconds, but only enableUpdates() is enough for the issue to occur in the default tab.
• Progressive bootstrap was disabled during tests above due to a bug in 3.3.6 (#5470#note-3) where tableviews are rendered as tables if not recreated with enableUpdates() and triggerUpdate(). Tables work fine.
• If progressive bootstrap is enabled and UI is recreated with enabledUpdates() + triggerUpdate(), then both tabs get broken after triggerUpdate().
• Issue observed with Wt 3.3.6 MSVC 2103 64bit binaries provided by Emweb.