fix(evaluate): reject exposeFunctions in the utility world

[Ayaan Gazali (ayaangazali)]

What is wrong today

exposeFunctions and the new world option cannot be combined, but passing both crashes inside the injected code instead of saying so. On aeebee1d2:

await page.evaluate(async ({ cb }) => await cb(17), { cb: x => x * 2 },
    { exposeFunctions: true, world: 'utility' });
// page.evaluate: TypeError: Cannot read properties of undefined (reading 'callBinding')

Same error from frame.evaluate and locator.evaluate. Reproduced on chromium, firefox and webkit.

Why

PageBinding.createInitScript installs the bindings controller as an init script, and init scripts only run in the main world, so globalThis[kBindingsControllerProperty] is undefined in the utility world. Runtime.addBinding is registered without a world, so the transport is there, but the controller that dispatches through it is not. That is also why the docs sentence saying an exposed function is "technically accessible from all frames and worlds of the page" does not hold:

await page.exposeFunction('f', x => x * 2);
await page.evaluate(() => window.f?.(21) ?? 'NOT PRESENT');                        // 42
await page.evaluate(() => window.f?.(21) ?? 'NOT PRESENT', undefined, { world: 'utility' }); // 'NOT PRESENT'

What this changes

Throws on the combination from assertEvaluateOptions, which every evaluate entry point already calls, and corrects the two doc sentences that promise all worlds. This matches the error JSHandleDispatcher.evaluateExpression already throws for a world it cannot serve.

If bindings are meant to work in the utility world, this guard is the wrong fix and I am happy to close it. The doc sentences would be the part worth keeping either way.

Verified with npm run flint green and tests/page/page-evaluate-world.spec.ts plus the seven adjacent evaluate/expose-function specs (173 tests) passing; the new test fails with the callBinding TypeError when the guard is reverted.

I am a freshman in college trying my best to contribute for the greater good, so please tell me if I have read the intent backwards here.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[Pavel Feldman (pavelfeldman)]

Please file an issue

[Ayaan Gazali (ayaangazali)]

Done, filed as #42686 with the reproducer and the root cause.

Noted on the issue-first rule, that is on me for opening this cold. I will lead with an issue from now on.