jpudysz
commented
2 months ago Thanks for the report! I need to ignore the IME insets (keyboard).
Closed dppo closed 2 months ago
jpudysz
commented
2 months ago Thanks for the report! I need to ignore the IME insets (keyboard).
jpudysz
commented
2 months ago Hmm I can't repro 🤔
Can you show me how to repro?
dppo
commented
2 months ago Hmm I can't repro 🤔
Screen.Recording.2024-07-04.at.17.21.04.mov
Can you show me how to repro?
I wrote a reproducible code this
mobily
commented
2 months ago hey @jpudysz! 👋 I'm having the same (?) issue. When I hide the keyboard and wait for a few seconds, there's some strange behavior happening. Unistyles is giving new insets values (see timestamps):
2024-07-05T10:11:00.092Z android insets {"bottom": 16, "left": 0, "right": 0, "top": 34}
2024-07-05T10:11:15.953Z android insets {"bottom": 327, "left": 0, "right": 0, "top": 34}
2024-07-05T10:11:31.128Z android insets {"bottom": 16, "left": 0, "right": 0, "top": 34}@dppo thank for the repo. I was able to repro it 🙏
I will create a patch
jpudysz
commented
2 months ago This is with extra patch -> if keyboard is visible then inset is 0. Without it it's little bit uglier:
Still wondering if it will break anything.
Description
when the keyboard pops up
miniRuntime.insets.bottom =
287 but in useSafeAreaInsets insets.bottom =
24
Steps to reproduce
console.log('miniRuntime.insets.bottom = ', miniRuntime.insets.bottom); console.log('miniRuntime.navigationBar.height = ', miniRuntime.navigationBar.height);
const insets = useSafeAreaInsets(); console.log('insets = ', insets.bottom);
LOG 11:40:05 AM | DEBUG : miniRuntime.insets.bottom =
287
LOG 11:40:05 AM | DEBUG : miniRuntime.navigationBar.height =
287
LOG 11:40:05 AM | DEBUG : insets =
24
Snack or a link to a repository (optional)
No response
Unistyles version
2.8.0
React Native version
0.74.3
Platforms
Android
Engine
Hermes
Architecture
Fabric (new)