feat: migrate KeyboardStickyView to reanimated#1307
Conversation
📊 Package size report
|
|
While at it, it would be nice to also allow reanimated shared values for the offset values :) |
|
@SamuraiF0x what is the use case of having "animated" offset? 🤔 Or why do you want to have padding as a shared value? |
|
@kirillzyusko It’s so I can animate the offset when closed, based on toolbar visibility - the toolbar visibility toggles depending on whether there is content inside input |
aa0c069 to
d991aa7
Compare
d991aa7 to
84c320d
Compare
|
Thanks @SamuraiF0x It makes sense what you are saying! I think a similar request has been made here: #1441 So I will try to think on how to add it! Hiding Toolbar dynamically and have an ability to adjust position of "frozen" |
|
LGTM |
|
@kirillzyusko Awesome! Screen.Recording.2026-04-29.at.12.07.59.mov |
📜 Description
Migrate
KeyboardStickyViewback to reanimated.💡 Motivation and Context
Animatedimplementation works well. However this component was originally developed using Reanimated and now I'm planning to extend its functionality:freezeproperty.Both things require better control over the animation management, so I'm switching back to reanimated implementation.
All the issues described in #898 seems to be resolved and
1.21.xrequires higher react-native version (where the issue has been fixed), so I think it's safe to go back to reanimated implementation now 🤞Closes #1306 #1273
📢 Changelog
JS
KeyboardStickyViewto reanimated;🤔 How Has This Been Tested?
Tested with e2e tests.
📸 Screenshots (if appropriate):
Everything works as before 🤷♂️
📝 Checklist