Open mkrecek234 opened 3 months ago
closing in favor of https://github.com/atk4/ui/issues/1988, I belive such improvent will fix this as well
Yes it would be fixed by using scrolling
class on table - however we would still need our own javascript (which today is performed by JsScroll) which automatically loads further pages if you scroll at the end. That is the beauty of JsScroll which is not supported yet by FUI scrolling
property as there is no callback.
There is another twist of this issue which is critical: I have a Tabs in a view - on a second tab I insert a grid with addJsPaginator, and say 2 rows. If the tab that I add it to is a static tab, the first data row is hidden behind the header row, as margin-top is set to 0px (erroneously).
If I change the tab to be a dynamically loading tab, the first data row is correctly shown below the header row (in my case the margin-top then is set to 46x....
Critical as data is not properly shown. I would opt to look into it, as refactoring to FUI scrolling with the javascript is too time-consuming and no contributor for that yet.
There is another twist of this issue which is critical: I have a Tabs in a view - on a second tab I insert a grid with addJsPaginator, and say 2 rows. If the tab that I add it to is a static tab, the first data row is hidden behind the header row, as margin-top is set to 0px (erroneously).
If I change the tab to be a dynamically loading tab, the first data row is correctly shown below the header row (in my case the margin-top then is set to 46x....
Critical as data is not properly shown. I would opt to look into it, as refactoring to FUI scrolling with the javascript is too time-consuming and no contributor for that yet.
please update your post above to contain minimal code to reproduce plus add screenshot
$g1->addJsPaginatorInContainer
which also activates fixed headersExpected result:
Today's behavior:
Screenshot: