-
Notifications
You must be signed in to change notification settings - Fork 742
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(listview): [Android] Improve performance when updating list items #6789
Conversation
Fix LayoutInformation.GetAvailableSize() to return availabe size before view-related constraints (MaxWidth, MaxHeight etc), and also to update after MeasureOverride() is called, in line with UWP as well as WASM and Skia.
When a property of an item in the list changes, ensure that only that item container is remeasured.
Ensure to call LayoutChild() every time, since the position may change even if measure hasn't changed (when scrolling, most obviously). Note that Android's internal layout caching logic ensures that ArrangeOverride() isn't called if not needed.
Oh iOS
The build 32201 found UI Test snapshots differences: Details
|
GitHub Issue (If applicable): closes #6754
When a property of an item in the list changes, ensure that only that item container is remeasured.
PR Type
What kind of change does this PR introduce?
What is the current behavior?
What is the new behavior?
PR Checklist
Please check if your PR fulfills the following requirements:
Screenshots Compare Test Run
results.Other information
Internal Issue (If applicable):