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
{{ message }}
Repository navigation
Refactor our viewport logic into a new RenderObject subclass hierarchy #4430
Rather than use RenderBox for viewports, we should invent a new render object protocol that is used for lazy viewporting and scrolling.
This protocol would have:
Inputs: main axis, main axis start offset, main axis end offset, cross-axis dimension
Outputs: main axis layout size, main axis offset consumed, paint phase (top, header, content)
Intrinsics: In some cases, we will need a way to enable intrinsic dimensions to propagate through (e.g. popup menus), but this is super expensive, so we should have a way to turn it on or off.
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.
Activity
abarth commentedon Jul 7, 2016
Started experimenting in https://github.com/abarth/flutter/tree/viewported
abarth commentedon Jul 11, 2016
inputs: min/max of start/end offset, main axis, cross axis extent, anchor
outputs: main axis extent, start/end offset
6 remaining items
abarth commentedon Feb 10, 2017
This is now RenderViewport2.
[fuchsia] Use AOT in release builds (flutter#4430)
github-actions commentedon Sep 5, 2021
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.