You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I am testing 5.0.0-b5 and found a bug in StickyHeaderHelper#translateHeader() on row 151. You are expecting next potential header on position 1. But if for example I use 3 columns in my grid, you will always get current header until all items in section are off the screen.
So you won't get this nice pushing of one header off the screen by another header.
I was able to reproduce this in your demo app, when I changed span count of grid to 3 and span size of all items except header to 1.
Anyway, thanks for great work.
The text was updated successfully, but these errors were encountered:
Hello @MartinRajniak, I've reproduced the issue using the fragment ExpandableSection using 3 for span count and size for non header items.
Indeed, it should enter in the if at line 155 to calculate the translation, but it doesn't.
Logging the item cotent with adapterPos it shows:
SubItem[id=E1S1, title=Sub Item 1 in expandable section]
SubItem[id=E1S2, title=Sub Item 2 in expandable section] but not the sub Item 3, then it swap the header, so it doesn't see where the section ends
swapHeader newPosition=5
SubItem[id=E2S2, title=Sub Item 2 in expandable section]
Hi,
I am testing 5.0.0-b5 and found a bug in StickyHeaderHelper#translateHeader() on row 151. You are expecting next potential header on position 1. But if for example I use 3 columns in my grid, you will always get current header until all items in section are off the screen.
So you won't get this nice pushing of one header off the screen by another header.
I was able to reproduce this in your demo app, when I changed span count of grid to 3 and span size of all items except header to 1.
Anyway, thanks for great work.
The text was updated successfully, but these errors were encountered: