-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[RNmobile] Enable inserter block search #33559
Conversation
Size Change: +1.2 kB (0%) Total Size: 1.08 MB
ℹ️ View Unchanged
|
@@ -45,7 +45,10 @@ import BottomSheetSubSheet from './sub-sheet'; | |||
import NavigationHeader from './navigation-header'; | |||
import { BottomSheetProvider } from './bottom-sheet-context'; | |||
|
|||
const DEFAULT_LAYOUT_ANIMATION = LayoutAnimation.Presets.easeInEaseOut; | |||
const DEFAULT_LAYOUT_ANIMATION_PROPERTIES = { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See the comment in the description regarding the reason for this change.
The issue only affects Android but the code path to the default animation is only followed by Android.
iOS is following the keyboard specific animation setup ( around line 123 in this diff ).
Regarding that, I did try to force Android into using the keyboard
animation type. The RN docs do not say that that animation type is iOS only but I kept running into this issue facebook/react-native#27839 ( I too confirmed that UIManager.setLayoutAnimationEnabledExperimental(true)
is set up correctly ).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tested this on iPhone and iPad sims and a physical Android device and all seems well. The animation issues with the bottom sheet appear resolved by these changes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On iOS, it works perfect but on Android, I noticed that we still have some visual glitches in the transition (see attached video capture), have you experienced this too? is it expected?
Tested on Samsung Galaxy S20 FE 5G (Android 10) with production JS bundle served via Metro.
Screen_Recording_20210802-110507_WordPress.Pre-Alpha.mp4
@fluiddot I'm seeing the same issues and flagged them with @jhnstn as a "blocker" for shipping this feature. We've been discussing some possible (Android-specific) workarounds and whether or not we should ship as-is then iterate to fix these animation issues. Regarding potential workarounds, I was thinking yesterday about how we might work around the height transition bugs by limiting the number of height transitions. I'm not 100% sure if I like this option because of the downsides I'll mention below, but one option I explored was going straight to the full-height sheet when the user taps the There are some downsides to that approach:
Here's a blueprint to help visualize this flow: |
closing in favor of #34129 |
Description
This enables the Inserter Block search feature on mobile Gutenberg.
Gutenberg Mobile companion PR wordpress-mobile/gutenberg-mobile#3735
How has this been tested?
The feature has been tested in #33237
Screenshots
Types of changes
Replace
__DEV__
flag withtrue
to enable the inserter search in production builds.It also addresses some feedback from @iamthomasbishop (wordpress-mobile/WordPress-Android#15044 (comment) ):
easeInEaseOut
toeaseIn
and lowering the duration from300
to150
. The idea is to reduce the attention that the existing animation draws while still preventing the visual glitch when the keyboard opens.Checklist:
*.native.js
files for terms that need renaming or removal).