fix: enabled prop behavior for KeyboardStickyView (fabric arch)#1312
Merged
kirillzyusko merged 1 commit intomainfrom Feb 21, 2026
Merged
fix: enabled prop behavior for KeyboardStickyView (fabric arch)#1312kirillzyusko merged 1 commit intomainfrom
enabled prop behavior for KeyboardStickyView (fabric arch)#1312kirillzyusko merged 1 commit intomainfrom
Conversation
Contributor
📊 Package size report
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
📜 Description
Fixed
enabledbehavior forKeyboardStickyViewon fabric.💡 Motivation and Context
It looks like on fabric when we detach animated value we "break" graph of native driver animations (sine we don't use Animated value anymore) and animations becomes just frozen (element is not getting moved to its initial position).
To overcome this problem I replaced plain
closedvalue withAnimatedone:Effectively we still consume
height, but we multiply it by0(we get0after that) and after that we make additions0+closedas animated value. As a result we always switch between animated values and we always useheightvalue (it was critical, if we stop to use it we get again the same bug).I used this code for testing:
📢 Changelog
JS
🤔 How Has This Been Tested?
Tested in example project manually.
📸 Screenshots (if appropriate):
Simulator.Screen.Recording.-.iPhone.17.Pro.-.2026-02-20.at.21.51.48.mp4
Simulator.Screen.Recording.-.iPhone.17.Pro.-.2026-02-20.at.21.53.04.mp4
📝 Checklist