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
The progressViewOffset property for the RefreshControl component is not functioning as expected. When setting an offset value, the refresh indicator does not move from its default position at the top of the view.
Reproduce
Steps to reproduce the behavior:
Go to a page with a scroll view that uses RefreshControl.
Set the progressViewOffset property to a numeric value, for example, 50.
Perform a pull-to-refresh action on the scroll view.
Observe that the refresh indicator remains at its default position and does not move down by 50 units as expected.
<RefreshControlprogressViewOffset={50}/>
Expected behavior
The refresh indicator should move 50 units down from its default position, aligning itself according to the progressViewOffset value set.
Smartphone:
Device: [iPhone 14, pro Max]
OS: [iOS 17.0]
Additional context
This issue limits the ability to create a polished and well-aligned user interface, especially when using custom headers or UI elements that need to align with the refresh indicator.
The text was updated successfully, but these errors were encountered:
Describe the bug
The
progressViewOffset
property for theRefreshControl
component is not functioning as expected. When setting an offset value, the refresh indicator does not move from its default position at the top of the view.Reproduce
Steps to reproduce the behavior:
RefreshControl
.progressViewOffset
property to a numeric value, for example,50
.Expected behavior
The refresh indicator should move 50 units down from its default position, aligning itself according to the
progressViewOffset
value set.Smartphone:
Additional context
This issue limits the ability to create a polished and well-aligned user interface, especially when using custom headers or UI elements that need to align with the refresh indicator.
The text was updated successfully, but these errors were encountered: