Repository navigation
Wait for native browser readiness before opening local HTML - #114
Merged
Merged
Conversation
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.
Opening a local HTML file immediately after creating a native browser page could fail with "Agent Browser page is still starting". Wait for page readiness before navigating, with bounded startup timeout and cancellation on session change or page closure. Preserve the existing unsaved-file guard, including a second guard if the editor changes while the page is being created.
Validation: native Windows WebView2 reproduced the failure and then loaded the encoded local HTML URL with the actual readiness helper; delayed-ready real App fixture passed keyboard activation, session ownership, save/cancel and error paths. Readiness/timeout/closed/cancellation unit tests, full Web tests/build, i18n generation, strict OpenSpec validation and diff checks passed. This Web-only fix is included before v1.0.0 tag publication.