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 onSafeAreaInsetsUpdatecallback in the BottomSheet component does not receive the expected values when a full screen sheet is rotated from portrait -> landscape -> portrait.
In the portrait orientation, open the block editor in WPiOS by creating a new post.
Tap the three dots at the top right.
Tap "Help & Support".
Observe that the top of the view is under the notch and observe the value for the resultobject in the callback.
Rotate the device into landscape.
Rotate the device back to portrait.
Observe that the top of the view is level with the notch and observe the value for the resultobject in the callback does not match the value from step 4 (specifically the safeAreaInsets.top value).
Expected behavior
The top of the sheet view abides by the Safe Area boundaries and safeAreaInsets is consistent for the two orientations.
Describe the bug
The
onSafeAreaInsetsUpdate
callback in the BottomSheet component does not receive the expected values when a full screen sheet is rotated from portrait -> landscape -> portrait.To Reproduce
Prerequisites:
Steps to reproduce:
result
object in the callback.result
object in the callback does not match the value from step 4 (specifically thesafeAreaInsets.top
value).Expected behavior
The top of the sheet view abides by the Safe Area boundaries and
safeAreaInsets
is consistent for the two orientations.Smartphone
1.64.0
Additional context
Please see previous discussions here.
We're currently using this library to compute the safe areas and we may need to consider an alternative approach.
The text was updated successfully, but these errors were encountered: