fix: align WebMCP consumer calls with Chrome 155 - #68
Merged
Merged
Conversation
naji247
approved these changes
Sep 23, 2026
kashishhora
changed the title
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.
Use object inputs in the bridge, with a guarded JSON-string fallback for older Chrome that preserves arguments and avoids retrying tool failures or cancellations.
Match native executeTool defaults: omitted or undefined input becomes a fresh empty object when options are omitted or undefined. Undefined input with supplied options still rejects. Update the polyfill, regression tests, native harness, and docs.
Validation: 291 tests pass; library and extension builds and type checks, lint, and the native-harness build pass. The harness passes in native Chrome 155.0.8059.2 and with the polyfill.