All rows must have a matching fixed height. The table cannot display partial rows.
In UI5, when a scroll event is performed, rather than scrolling the table container by 1px as is typical when performing a scroll, the scroll event is caught and prevented, the <tr> elements are fixed in place, and the data from each row is moved up or down to the previous or next row(s) depending on the scroll direction. This provides a snappier feel from a UX perspective and also eliminates some edge case problems such as #11443 because there is no way to have the table only showing a partial row (also due to the fixed height of rows)
If a cell is focused, and the user scrolls, the focused cell position stays the same, effectively making a different cell focused:
This is tricky to explain, because from the developer's perspective, it's the same <td> that is focused. But from the user's perspective, the focus has changed cells.
If a table cell has some child element that is actionable by the user such as a text input, a scroll event on the table should be considered as a "submit" action by the user
This will be released as a significant breaking change to the existing virtual scrolling functionality of the platform table. If these changes are downported to a previous version of fundamental-ngx, it will need to be released as a separate feature, so as to not break the existing functionality for users on fundamental-ngx using ng15 etc
The table scrolling behavior must be reworked to more closely match that of the ui5 grid table: https://sapui5.hana.ondemand.com/#/entity/sap.ui.table.Table/sample/sap.ui.table.sample.Basic
Notable differences are:
<tr>
elements are fixed in place, and the data from each row is moved up or down to the previous or next row(s) depending on the scroll direction. This provides a snappier feel from a UX perspective and also eliminates some edge case problems such as #11443 because there is no way to have the table only showing a partial row (also due to the fixed height of rows)https://github.com/SAP/fundamental-ngx/assets/2471874/6495c774-6840-4d3c-b8c9-2cba0f6b799b
This is tricky to explain, because from the developer's perspective, it's the same
<td>
that is focused. But from the user's perspective, the focus has changed cells.This will be released as a significant breaking change to the existing virtual scrolling functionality of the platform table. If these changes are downported to a previous version of fundamental-ngx, it will need to be released as a separate feature, so as to not break the existing functionality for users on fundamental-ngx using ng15 etc