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
If you open the block picker and then rotate the device, the block picker layout is messed up. Not all blocks appear on screen and there's no way to navigate to them. The only solution is to close the block picker and reopen it.
Steps to reproduce
With the device in portrait mode, start a new post.
Open the block picker.
Rotate the device to landscape. Note that the blocks don't use the full width of the screen and not all blocks fit on screen.
Close the block picker and reopen it.
Rotate the device to portrait. Note that some blocks don't appear on screen.
In addition, rotating the device with the block picker open on Android makes the keyboard appear. This doesn't cause any issues once the keyboard is closed, but it does interfere with viewing/interacting with the block picker.
Screenshots
iOS - rotating portrait to landscape:
iOS - rotating landscape to portrait (8 blocks instead of 10):
In addition, rotating the device with the block picker open on Android makes the keyboard appear. This doesn't cause any issues once the keyboard is closed, but it does interfere with viewing/interacting with the block picker.
If you open the block picker and then rotate the device, the block picker layout is messed up. Not all blocks appear on screen and there's no way to navigate to them. The only solution is to close the block picker and reopen it.
Steps to reproduce
In addition, rotating the device with the block picker open on Android makes the keyboard appear. This doesn't cause any issues once the keyboard is closed, but it does interfere with viewing/interacting with the block picker.
Screenshots
iOS - rotating portrait to landscape:
iOS - rotating landscape to portrait (8 blocks instead of 10):
Android - rotating portrait to landscape:
Android - rotating landscape to portrait:
Tested on:
The text was updated successfully, but these errors were encountered: