feat(addInitScript): allow passing functions as init script arguments#41921
Merged
pavelfeldman merged 1 commit intoJul 21, 2026
Merged
Conversation
dcrousso
approved these changes
Jul 21, 2026
Contributor
Test results for "MCP"7792 passed, 1269 skipped Merge workflow run. |
Contributor
Test results for "tests 1"Warning The triggering workflow run ended with status 5 flaky50106 passed, 1190 skipped Merge workflow run. |
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.
Summary
page.addInitScript()andbrowserContext.addInitScript()now accept functions insideargwhen called with the new{ exposeFunctions: true }option, following feat(evaluate): allow passing functions as evaluate arguments #41801.noGlobalbindings that are re-installed in every new document, so unlikeevaluate(), they survive navigations.