[Tables] Scrollable area in tables much longer than content

[akhenry]

In historical tables (but problem is probably in mct-table directive and thus not specific to historical tables) the scroll bar allows scrolling well beyond the visible rows of the table.

It looks as though the table in question (historical table with Sine Wave Generator content) probably has many more rows than the 50 displayed, but these are not being rendered for some reason. 50 is a suspicious number as it is the size of the maxDisplayRows variable that determines when the scrolling logic kicks in in the setVisibleRows function. This is where I would look first.

[larkin]

Might also be a change to html/css with the control bars that causes the wrong element to scroll.

[akhenry]

Have confirmed data loss is occurring in real-time and historical tables.

[akhenry]

Ah, it's super easy. It's due to selecting the wrong element against which to process scroll events. It selects the first child div, which has changed since initial implementation. This needs to be a little more robust.

[akhenry]

Might also be a change to html/css with the control bars that causes the wrong element to scroll.

Yup, this is basically it.

[larkin]

Testathon 2016-10-21: Can't validate in historical tables, appears fixed in realtime tables.

[charlesh88]

Testathon 2016-10-21: Verified in RT Table objects and views. Can't validate in historical tables via WARP.

[akhenry]

Fix was in MctTable directive, so applies to historical tables also.