Repository navigation
fix: recover native UI synchronization without navigation - #325
Merged
Merged
Conversation
Contributor
Playwright test resultsDetails
|
Contributor
|
📊 Ionic 9 Playwright Test Report View the detailed Ionic 9 report after GitHub Pages deployment completes: https://rdlabo-dev.github.io/ionic-theme-ios27/pr-325/ Ionic 8 runs against the same screenshots in a separate matrix job. View both results in the workflow run. |
Contributor
npm beta publishedCI passed for the merge commit npm install @rdlabo/ionic-theme-ios27@2.0.2-beta.pr325.sha8a1b6915815f @rdlabo/capacitor-native-ui@2.0.2-beta.pr325.sha8a1b6915815f |
This was referenced Oct 23, 2026
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.
Native UI synchronization can remain stale without a bridge error: an update reaches native while projection is retained, its acknowledgement is skipped, and the DOM returns to the previously accepted state. Snapshot deduplication then prevents reconciliation until another change, such as navigation, forces an update.
Invalidate the cached snapshot when sending an update so an interrupted acknowledgement cannot suppress the next synchronization. Also retry one rejected update by reading the latest DOM through the existing scheduler, keeping the connection and listeners intact. Do not replay input; reject unacknowledged input between attempts. A second consecutive failure or a revision mismatch retains the existing stop-and-restore behavior.
Tradeoffs:
Validation:
The reported intermittent Duo tab-switching incident has not been reproduced on the simulator; these tests establish specific failure paths, not its confirmed root cause. This does not re-register a lost event listener or reconnect a stopped runtime.