First time i open a branch it does not take the height but second time it does. However, in the snippet it does.
It seems to be disabled, watching that light grey background color and it does not scroll. Why? in next snippet, it has a white background color but is not scrolling.
Though I couldn’t repeat the behaviour you’ve shown by screenshots, I can confirm the issue with list scrolling. So, you need to apply the following changes to your code:
remove autoheight parameter from datatable constructor, otherwise it is not scrolled even in the desktop;
add scrollAlignY parameter to the datatable (docs);
The background color of the list (subview) is light grey, like being disabled.
Is this ok?
list height (type: { height: “350” }) is supposed to be for each element, is not it? In my mobile, it takes that height for all elements. Second one is cut.
I set 1000 for example and now i see 3 elements, but there are more elements in the list.
The “problem” with first open ans second time still persists, like screenshots i sent you.
(2) Yes, it is the height for each data element while the total height is calculated as item height * item count. Is the autoheight enabled for your subview list?
(3) I have tested the snippet in the native browser of the Android 4.4.2 but the problem didn’t show up.
yes, i tried it through my mobile web browser and works. However, same code in my hybrid cordova app does not.
It is like that autoheight property is set to false first time and second time is set to true.
On the other hand, that light grey color only appears in my hybrid app too. In my web browser does not. i will try to remove that css style and set my own style. Your snippet seems to be other than you want it to share with me or i do not understand it.
Also, when using lists, with last item, there is some space left at the bottom of that element. I usually add a layout row with a height of 40 and that fixes the problem.
Now, in this datatable, there is the same “problem” and i tried to include that list into a layout and set it to the datatable subview. But that does not solve the issue.