On Wed, Jul 9, 2025 at 11:06 AM David Bokan <bo...@chromium.org> wrote:
> Thanks! Filled these out in chromestatus - posting inline replies below as > well. > > On Wednesday, July 9, 2025 at 1:48:42 PM UTC-4 Reilly Grant wrote: > > On Wed, Jul 9, 2025 at 9:36 AM David Bokan <bo...@chromium.org> wrote: > > Contact emailsbo...@chromium.org, hvanops...@chromium.org, khushalsagar@ > chromium.org > > ExplainerNone - We're working to publish an explainer ASAP and will link > it on this thread when it's available. > > SpecificationNone > > Summary > > Script Tools enable authors to expose JavaScript APIs on their site for > automated use by the user agent. They allow an author to annotate these > APIs with descriptions and provide input schema, allowing automation > frameworks a more specific method to access the site's functionality. > > > Blink componentBlink > <https://issues.chromium.org/issues?q=customfield1222907:%22Blink%22> > > Blink>WebML > > Please create a sub-component for Script Tools under either Blink>WebML or Blink>AI because my team uses Blink>WebML for WebNN issues and is tracking this component with our internal project management tools so having non-WebNN issues filed here will cause confusion. > Motivation > > Automation over web pages is an increasingly active area. Currently, web > APIs provide no direct way to interact with automation frameworks so these > frameworks rely on simulating user input on pages. Script Tools aims to > provide a way for participating web sites to provide automation-specific > paths in their UI. Automation can then proceed more quickly and enables the > web site's UI to react. > > > Initial public proposalNone > > TAG reviewNone > > TAG review statusPending > > Risks > > > Interoperability and Compatibility > > None > > Please fill out this section. > > > Given this is a new space and new API - there's no compatibility risk. > > Usual risk related to other browser vendors not adopting the API apply. > This API is meant to augment capabilities provided by browser add-ons and > so non-adoption in other engines would have limited user-impact and thus we > consider the risk to be low. > > *Gecko*: No signal > > *WebKit*: No signal > > *Web developers*: No signals > > *Other signals*: > > WebView application risks > > Does this intent deprecate or change behavior of existing APIs, such that > it has potentially high risk for Android WebView-based applications? > > None > > > Debuggability > > None > > > Is this feature fully tested by web-platform-tests > <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> > ?No > > I assume this will be tested eventually. Are there any blockers to being > able to test it with WPT? > > > That's right, the "No" is to currently but the intent is to eventually > test in WPT as much as possible. > > Since the API provides the user agent with the ability to call certain > tools, we might need to extend the WPT harness to support this. At minimum > the IDL and basic usage can and will be tested in WPT. > > > > > Flag name on about://flagsNone > > Finch feature nameNone > > Non-finch justificationNone > > Requires code in //chrome?True > > Estimated milestones > > No milestones specified > > > Link to entry on the Chrome Platform Statushttps://chromestatus.com/ > feature/5117755740913664?gate=5183588999626752 > > This intent message was generated by Chrome Platform Status > <https://chromestatus.com/>. > > -- > You received this message because you are subscribed to the Google Groups > "blink-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to blink-dev+unsubscr...@chromium.org. > To view this discussion visit https://groups.google.com/a/ > chromium.org/d/msgid/blink-dev/CANMmsAtRdyRw1WtO5va0K%3D_ > adYH-FRh01xvw5%2BosSd_DAq%3D%3DUQ%40mail.gmail.com > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CANMmsAtRdyRw1WtO5va0K%3D_adYH-FRh01xvw5%2BosSd_DAq%3D%3DUQ%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAEmk%3DMZyZF72qQoCdZnaZg3Sz-7zOpuLBc%2BtKRt0a6u0yJ8QFQ%40mail.gmail.com.
