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
Thank you for all your work on this great package!
I encountered this issue when I included a MasonryGridView in 3 separate tabs. This issue happens when scrolling, switching tabs, and going back or some combination thereof.
To consistently reproduce it, scroll to the last item in "Tab 1". Then switch to "Tab 2" and then switch back to "Tab 1". In "Tab 1" the MasonryGridView jumps almost to the top which is unexpected. PageStorageKey should maintain the state just like for GridView and ListView.
I am using Flutter 3.19.6, Dart 3.3.4, and 0.7.0 of the package.
Here is the code to reproduce the issue. I've included GridView and ListView builders so you can see that the scroll position is preserved for them. Just comment out and uncomment as needed.
Any chance this could be fixed soon so we can show off this cool masonry view to our users?
I have the same problem, I used GridView and it worked as expected but when I switched it with MasonryGridView because of the UI improvement, I can not keep the scroll position when I change the page and come back. Anysuggestions or any advice might be very helpful.
Thank you for all your work on this great package!
I encountered this issue when I included a
MasonryGridView
in 3 separate tabs. This issue happens when scrolling, switching tabs, and going back or some combination thereof.To consistently reproduce it, scroll to the last item in "Tab 1". Then switch to "Tab 2" and then switch back to "Tab 1". In "Tab 1" the
MasonryGridView
jumps almost to the top which is unexpected.PageStorageKey
should maintain the state just like forGridView
andListView
.I am using Flutter 3.19.6, Dart 3.3.4, and 0.7.0 of the package.
Here is the code to reproduce the issue. I've included
GridView
andListView
builders so you can see that the scroll position is preserved for them. Just comment out and uncomment as needed.Any chance this could be fixed soon so we can show off this cool masonry view to our users?
The text was updated successfully, but these errors were encountered: