Replies: 1 comment 2 replies
-
{
...
"dependencies": {
"@webview-bridge/react-native": "^1.7.6",
"expo": "53.0.11",
"expo-blur": "~14.1.5",
"expo-clipboard": "~7.1.4",
"expo-constants": "~17.1.5",
"expo-dev-client": "~5.2.4",
"expo-font": "~13.3.1",
"expo-haptics": "~14.1.4",
"expo-image": "~2.3.0",
"expo-linear-gradient": "~14.1.5",
"expo-linking": "~7.1.4",
"expo-router": "~5.1.0",
"expo-splash-screen": "~0.30.9",
"expo-status-bar": "~2.2.3",
"expo-symbols": "~0.4.5",
"expo-system-ui": "~5.0.8",
"expo-web-browser": "~14.1.6",
"lodash.debounce": "^4.0.8",
"react": "19.0.0",
"react-dom": "19.0.0",
"react-native": "0.79.3",
"react-native-config": "^1.5.5",
"react-native-gesture-handler": "~2.24.0",
"react-native-reanimated": "~3.17.4",
"react-native-safe-area-context": "5.4.0",
"react-native-screens": "~4.11.1",
"react-native-size-matters": "^0.4.2",
"react-native-web": "~0.20.0",
"react-native-webview": "^13.15.0",
"react-native-keyboard-controller": "^1.17.5",
......
},
}
|
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I embedded a lexical editor inside a WebView and wrapped it with the KeyboardAwareScrollView component, expecting it to scroll to the optimal editing position. However, it seems KeyboardAwareScrollView's adaptation for WebView components isn't complete.
e4477b03aa1a71d7654083124ba13f45.mp4
The phenomenon I observed (also shown in my video) can be described as follows: For WebView, KeyboardAwareScrollView's scrolling logic doesn't seem fully adapted. When initially clicking the WebView to give it focus, the WebView may scroll to an appropriate position (but without animation, possibly with a slight flicker). Then when losing focus and regaining it, keyboard avoidance may not work properly.
By clicking to switch to the textInput component below the WebView, repeatedly switching focus may restore normal scrolling logic (as I expected) for the WebView. Then everything works fine. But later, under unknown triggering conditions, the WebView component reverts to its original state.
This behavior seems strange to me. I'm not sure if it's a bug, so I'd appreciate your insights. I'd like to understand the framework's adaptation status for WebView.
Below is the code that reproduces this behavior (as shown in the video above):
Beta Was this translation helpful? Give feedback.
All reactions