Connect declarative form tools to ActorTask::Pause [10/N] This CL implements the mechanism to pause actor execution when a declarative WebMCP form tool requires user interaction. This happens when the `toolautosubmit` attribute is absent, and the renderer is waiting for the user to click the submit button. Key changes: - Added the `ScriptToolHost` Mojo interface to allow the renderer to request execution pauses from the browser. - Implemented `ModelContext::PauseExecution` in Blink to trigger this IPC. - Updated `HTMLFormElement` to call `PauseExecution` when a declarative tool is invoked without auto-submission. - Added `ActorScriptToolReceiver` in the browser process to receive the IPC and call `ActorTask::Pause(true)` for the corresponding task. Bug: 475992364 Fixed: 477323944 Change-Id: I577c8af866bfe822f16b1fc35dbedf1cbebc7009 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7543077 Reviewed-by: Ben Greenstein <bengr@chromium.org> Reviewed-by: Elly FJ <ellyjones@chromium.org> Commit-Queue: Mason Freed <masonf@chromium.org> Cr-Commit-Position: refs/heads/main@{#1580338}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.