The issue we are seeing happens immediately following a hard browser refresh. After a swimlane has been collapsed, it auto expands while scrolling vertically. I have not been able to reproduce the issue in your demo code.
Board configuration:
5 Columns
6 Swimlanes
stickyHeaders = true
Data is distributed in a single column, roughly 100 cards per swimlane.
Pagination = we set event listeners on the page scroll - vertical and horizontal (if it exists) to load more cards vertically or horizontally.
We initially load 8 rows of cards. All columns and swimlanes are expanded by default. We need to scroll down 10 times to see the next swimlane.
STR:
- After page load, collapse the first swimlane
- Start scrolling down the page (2nd swimlane become sticky momentarily).
Expected Behavior:
1st swimlane is still collapsed
Actual Behavior:
1st swimlane becomes sticky and is expanded.
I think this is a side effect of how we load data into the board. Even though we collapsed the 1st swimlane the next vertical scroll will continue to load more records into the store for the 1st swimlane, until all of the records for the 1st swimlane are loaded, then we fetch the records for the 2nd swimlane and exhaust the 2nd swimlane records, then the 3rd ... .
So my question: Is there logic in the board to auto-expand a swimlane when new records are rendered into it? If yes, then can this behavior be suppressed?
