| Auto-Submit | +1 |
| Commit-Queue | +1 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
third_party/blink/* LGTM. I didn't review chrome/*.
return fail(WebDocument::ScriptToolError::kInvalidInputArguments);Since all of the `fail()` cases are `kInvalidInputArguments`, perhaps we just hard-code that and avoid passing it?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Auto-Submit | +1 |
| Commit-Queue | +1 |
return fail(WebDocument::ScriptToolError::kInvalidInputArguments);Since all of the `fail()` cases are `kInvalidInputArguments`, perhaps we just hard-code that and avoid passing it?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
tooldescription="A declarative WebMCP tool"nit: Did we want to use tool-name instead of toolname?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +0 |
class DeclarativeWebMCPTool {nit: The code uses the old name, ScriptTool for imperative WebMCP. Perhaps we should use a name like HTMLElementTool?
| Code-Review | +1 |
third_party/blink/public/web/web_document.h LGTM
| Code-Review | +1 |
Ok, I'd prefer returning an explicit status rather than overloading the presence of the string, but its not crucial.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
tooldescription="A declarative WebMCP tool"nit: Did we want to use tool-name instead of toolname?
@mas...@chromium.org switched to toolname, some restriction about the hyphen ones being used for custom attributes.
class DeclarativeWebMCPTool {nit: The code uses the old name, ScriptTool for imperative WebMCP. Perhaps we should use a name like HTMLElementTool?
Naming is a mess because of the mix of WebMCP and script tool. I'd like us to do a pass once the spec name is finalized. I still lean on a name which includes the feature to make it explicit which tool we're talking about. Other features are adding tools as well now (like prompt API).
Declarative WebMCP: Add blink -> chrome API for cross-document case
Add the API to indicate when form submission uses the default action to
trigger a navigation.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
<!DOCTYPE html>From what I can see, this file is not tested in `chrome/browser/actor/tools/script_tool_browsertest.cc`. Is that intentional?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
<!DOCTYPE html>From what I can see, this file is not tested in `chrome/browser/actor/tools/script_tool_browsertest.cc`. Is that intentional?
Nvm. I just found out it was used later in https://chromium-review.googlesource.com/c/chromium/src/+/7512307