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
As a follow up of the offset changes mentioned at the end of #30, this issue occurs when the content view controller is a scroll view, e.g., a UITableView which gets scrolled programmatically, e.g., by using scrollToRow(at: IndexPath, at: ScrollPosition, animated: Bool).
Expected result
Moving the floating panel, e.g., from .half to .fullafter using scrollToRow or similar programmatic ways to scroll a scroll view should not cause a change in the contentOffset of the scroll view. Video
Actual result
Moving the floating panel after using programmatic ways to scroll a scroll view will set the contentOffset to contentOffsetZero causing the content to jump to the top. Video
Note
Changing the code to achieve the expected result would also cause that manually scrolled scrollviews are not at contentOffsetZero when the floating panel is moved from .full to .half, as mentioned in #30 (comment). But this would align with the behavior of Apple's Maps and Stocks apps.
The text was updated successfully, but these errors were encountered:
As a follow up of the offset changes mentioned at the end of #30, this issue occurs when the content view controller is a scroll view, e.g., a
UITableView
which gets scrolled programmatically, e.g., by usingscrollToRow(at: IndexPath, at: ScrollPosition, animated: Bool)
.Expected result
Moving the floating panel, e.g., from
.half
to.full
after usingscrollToRow
or similar programmatic ways to scroll a scroll view should not cause a change in thecontentOffset
of the scroll view.Video
Actual result
Moving the floating panel after using programmatic ways to scroll a scroll view will set the
contentOffset
tocontentOffsetZero
causing the content to jump to the top.Video
Note
Changing the code to achieve the expected result would also cause that manually scrolled scrollviews are not at
contentOffsetZero
when the floating panel is moved from.full
to.half
, as mentioned in #30 (comment). But this would align with the behavior of Apple's Maps and Stocks apps.The text was updated successfully, but these errors were encountered: