Denis Hilt

@erikjons Thanks for using vscroll/ngx-ui-scroll! The issue you are experiencing is about getting the DOM elements parameters. In current implementation, for example, the height param is getting through the getBoundingClientRect...

@Fasteroid Thank you for the contribution to the topic! By the way, is there any chance to get a demo on stackblitz/codesandbox/whatever? It might be very helpful for others to...

Hi @s137, hi all! While I still can't provide table layout support (lack of Angular skills and time, any help would be appreciated), there is a good workaround. The thing...

Yes, as it follows from the doc -- "viewport height must be constrained". Regarding to routing stuff, we have no demo, but may be this story can help you: https://github.com/angular-ui/ui-scroll/issues/83....

@ornic If you are going to augment Viewport module, an easier approach might be as follows. Template: ```html ``` Directive: ```js .directive('uiScrollViewport', function () { return { restrict: 'A', scope:...

I didn't meet any issues with the Adapter when using the suggested approach.

https://github.com/dhilt/ngx-ui-scroll -- this lib (Angular) supports dynamic heights and has a lot of demo samples @vitalif I'm sorry to be so forward, but perhaps it might be a good idea...

@vitalif oh I see... the thing is the scroller in this demo does not know the viewport' height on start, it doesn't try to emulate invisible rows, that's why the...

@MiguelAngel82 Your template looks unpredictable from the point of the veiwport logic due to `thead` section placed between `ui-scroll-viewport` and `ui-scroll` containers. This `thead` may conflict with internal ui-scroll top...

@MiguelAngel82 You can apply a single-tr approach in your template: ``` ... data 1 ... edit data 1 ... data 2 ... edit data 2 ... ``` This would require...