fix: eliminate keyboard inset lag by caching safe area insets#457
Open
christianjuth wants to merge 1 commit intomainfrom
Open
fix: eliminate keyboard inset lag by caching safe area insets#457christianjuth wants to merge 1 commit intomainfrom
christianjuth wants to merge 1 commit intomainfrom
Conversation
Previously each keyboard show/hide event triggered an async getSafeAreaInsets() bridge call before updating CSS variables, adding a native round-trip on the critical path. Now we cache the last known insets and call applyInsets() synchronously, so --ion-safe-area-bottom updates immediately when keyboard events fire. https://claude.ai/code/session_015FFzwNvFkSWLBhv6f68LGH
Contributor
Dependency Graph
One node per top-level folder in |
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
2 participants
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.
No description provided.