Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: On-device Web Speech API

Great, thanks Peter! On Thu, Jun 12, 2025 at 9:51 AM Peter Beverloo wrote: > Hey Rick, I'm replying in Ashley's absence - thank you for the added > context, & we have no concerns with unprefixing the existing Web Speech API > :) > > Thanks, > Peter > > > On Thu, Jun 12, 2025 at 2:29 PM Rick Byer

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: On-device Web Speech API

Hey Rick, I'm replying in Ashley's absence - thank you for the added context, & we have no concerns with unprefixing the existing Web Speech API :) Thanks, Peter On Thu, Jun 12, 2025 at 2:29 PM Rick Byers wrote: > Hi Ashley, > Thanks for catching this, I'm glad to see the WebView API exposure

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: On-device Web Speech API

Hi Ashley, Thanks for catching this, I'm glad to see the WebView API exposure process working :-). The context is that the web speech API is indeed old and supported on all platforms, but historically exposed only via a webkit prefix. Evan is adding on-device web speech which I understand is a desk

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: On-device Web Speech API

Looking a bit more deeply into this, am I right in understanding that there isn't really any new API being added? it looks like unprefixing is actually a tangent from the original scope of this I2S? So I may have gotten confused about what's actually going on. I found https://chromestatus.com/f

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: On-device Web Speech API

Hello, Blink and Web Speech API folks! I noticed from my Android WebView webexposed watchlist that https://chromium-review.googlesource.com/c/chromium/src/+/6422562 progresses towards the removal the "webkit" prefix from the Web Speech API. >From what I understand, this I2S (and Chrome Status)

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: On-device Web Speech API

LGTM3 On Wednesday, May 28, 2025 at 8:09:48 AM UTC-7 Chris Harrelson wrote: > LGTM2 > > On Wed, May 28, 2025 at 8:07 AM Vladimir Levin > wrote: > >> LGTM1. Please update the TAG thread with the spec changes for posterity >> On Tuesday, May 27, 2025 at 7:18:44 PM UTC-4 ev...@google.com wrote: >>

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: On-device Web Speech API

LGTM2 On Wed, May 28, 2025 at 8:07 AM Vladimir Levin wrote: > LGTM1. Please update the TAG thread with the spec changes for posterity > On Tuesday, May 27, 2025 at 7:18:44 PM UTC-4 ev...@google.com wrote: > >> Hi all, >> >> The spec changes have been merged and are live! >> https://webaudio.gith

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: On-device Web Speech API

LGTM1. Please update the TAG thread with the spec changes for posterity On Tuesday, May 27, 2025 at 7:18:44 PM UTC-4 ev...@google.com wrote: > Hi all, > > The spec changes have been merged and are live! > https://webaudio.github.io/web-speech-api/ > > I believe this should be ready for Blink owne

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: On-device Web Speech API

Hi all, The spec changes have been merged and are live! https://webaudio.github.io/web-speech-api/ I believe this should be ready for Blink owners to take another look. Please let me know if you have any questions. Thanks, Evan On Wed, May 21, 2025 at 10:33 AM Evan Liu wrote: > Hi! We discuss

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: On-device Web Speech API

Hi! We discussed this at the Audio Working Group and reached a consensus :) I have a PR out to update the spec and another one to update the explainer with the changes. I believe this should

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: On-device Web Speech API

Any conclusions from the WG meeting? On Wednesday, May 14, 2025 at 8:11:49 PM UTC+2 ev...@google.com wrote: > It would definitely be better to make this change before the feature > ships, but it's up to y'all Blink owners if you think this should be a > blocker for this intent. The Audio Workin

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: On-device Web Speech API

It would definitely be better to make this change before the feature ships, but it's up to y'all Blink owners if you think this should be a blocker for this intent. The Audio Working Group is meeting tomorrow morning so hopefully we'll be able to reach a consensus then! On Wed, May 14, 2025 at 8:0

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: On-device Web Speech API

On Wednesday, May 7, 2025 at 8:50:12 PM UTC+2 ev...@google.com wrote: Hi all, Thanks for the thorough review! I've opened a GitHub issue for the remaining request. Hopefully we'll settle on an option before the next Audio Working Group

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: On-device Web Speech API

Hi all, Thanks for the thorough review! I've opened a GitHub issue for the remaining request. Hopefully we'll settle on an option before the next Audio Working Group meeting on 5/15! I'll update the spec as soon as we do. Thanks, Evan On W

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: On-device Web Speech API

Thanks Evan and Jeff. Evan: if we can get to API symmetry, I think that will help considerably. Evan/Jeff: this seems like good advice from the TAG. When do we think we can get the bikeshed repain...er...develop updated names? Best, Alex On Wednesday, May 7, 2025 at 12:12:29 AM UTC-7 Jeffrey

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: On-device Web Speech API

FYI, the TAG finished our review with https://github.com/w3ctag/design-reviews/issues/1038#issuecomment-2853142041. We were generally happy with the design decisions that Evan and the WG have made, but we were still concerned that "ondevice-only" excludes some choices that future UAs might reasonab

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: On-device Web Speech API

Hi Alex, Sure, if adding support for these two options would make the API easier to approve, then we might as well include it! Thanks, Evan On Mon, May 5, 2025 at 11:09 AM Alex Russell wrote: > Does "trivial" mean "possible within the scope of this Intent"? Or does > that mean it will need to

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: On-device Web Speech API

Does "trivial" mean "possible within the scope of this Intent"? Or does that mean it will need to be picked up in the future? A full parity API is easier to approve. On Thursday, April 24, 2025 at 8:48:18 AM UTC-7 ev...@google.com wrote: > Hi Domenic, > > On-device Web Speech supports phrases l

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: On-device Web Speech API

Hi Domenic, On-device Web Speech supports phrases list, continuous, and all of the audio events. Support for interimResults and maxAlternatives isn't implemented at this time, but adding it would be trivial. Thanks, Evan On Tue, Apr 22, 2025 at 9:34 PM Domenic Denicola wrote: > Hi Evan, > > Ca

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: On-device Web Speech API

Hi Evan, Can you confirm that this new mode will support all the features of the existing speech recognition API? In particular, I am wondering about: - phrases list - continuous: true vs. false - interimResults: true vs. false - maxAlternatives: 1 vs. larger values - All the even

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: On-device Web Speech API

Hi Dan, For the second one, yes this change would be made prior to shipping. The second two changes might be a little more controversial, so I was planning on making those changes in subsequent PRs. Thanks, Evan On Mon, Apr 21, 2025 at 11:42 AM 'Dan Clark' via blink-dev < blink-dev@chromium.org>

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: On-device Web Speech API

Thanks Evan for the follow-up. The response to the TAG feedback mentions a few changes that would be web-facing: - Removing "cloud-only" - Changing installOnDevice to support multiple langs in a single call, including the consideration of a more expressive return value type. - Adding an AbortSi

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: On-device Web Speech API

Hi all, We discussed the TAG feedback at the Audio Working Group meeting yesterday and I've posted our response here: https://github.com/w3ctag/design-reviews/issues/1038#issuecomment-2815982645 Please let me know if anyone has any questions/comments/concerns. I don't think there's any particula

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: On-device Web Speech API

Just linking this up as I see there are some questions, but the opening post seems to suggest there are positive signals from WebKit... https://github.com/WebKit/standards-positions/issues/443 On Wednesday, April 16, 2025 at 10:55:52 AM UTC-4 Rick Byers wrote: > On Tue, Apr 15, 2025 at 8:14 PM

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: On-device Web Speech API

On Tue, Apr 15, 2025 at 8:14 PM Evan Liu wrote: > Thanks for the detailed feedback, Jeffrey! We'll discuss this at the Audio > Working Group meeting this week and I'll update this thread afterwards. > > Thanks, > Evan > > On Mon, Apr 14, 2025 at 9:08 PM Jeffrey Yasskin > wrote: > >> FYI, the TAG

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: On-device Web Speech API

Thanks for the detailed feedback, Jeffrey! We'll discuss this at the Audio Working Group meeting this week and I'll update this thread afterwards. Thanks, Evan On Mon, Apr 14, 2025 at 9:08 PM Jeffrey Yasskin wrote: > FYI, the TAG left comments at > https://github.com/w3ctag/design-reviews/issue

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: On-device Web Speech API

FYI, the TAG left comments at https://github.com/w3ctag/design-reviews/issues/1038#issuecomment-2803693504 . On Fri, Apr 4, 2025 at 10:22 AM Evan Liu wrote: > Are you thinking it might be reasonable to ship in M128 (decide by branch >> on Apr 28, plan to merge any required changes before May 21

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: On-device Web Speech API

> > Are you thinking it might be reasonable to ship in M128 (decide by branch > on Apr 28, plan to merge any required changes before May 21)? That sounds like a reasonable target, assuming TAG doesn't propose any significant changes. That said, if you want to, I'm supportive of shipping the unpr

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: On-device Web Speech API

> > This all looks great to me! Are you thinking it might be reasonable to > ship in M128 (decide by branch on Apr 28, plan to merge any required > changes before May 21)? > Off by one, classic. I think you meant 1*3*8 here. I know it's obvious now, but someone might once look back at this in ten

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: On-device Web Speech API

Thanks Evan! This all looks great to me! Are you thinking it might be reasonable to ship in M128 (decide by branch on Apr 28, plan to merge any required changes before May 21)? Paul, thank you for your comments, to what extent are your concerns now addressed? While we don't generally wait for ful

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: On-device Web Speech API

Hi all, I've addressed the following issues and re-requested a review for this. ✓ Worked with pade...@mozilla.com and others from the Audio WG in finalizing the API shape for on-device speech recognition. ✓ Expanded WPT coverage for on-device functionality ✓ Dropped the "webkit" prefix from the W

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: On-device Web Speech API

All, Answering with both hats separately here: Mozilla developer implementing this, and chair of the CG in which this is happening (and of the WG that will adopt this when it's rechartering time). While we (Mozilla) are extremely happy to see work in the area, are participating in the standard

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: On-device Web Speech API

On Tue, Jan 21, 2025 at 7:33 PM Evan Liu wrote: > So are you OK with adding unprefixing to this intent (or if you prefer, a >> new one that this is blocked on)? > > Yeah, I think that's a great idea! I'm also in favor of tracking usage of > the prefixed version with the goal of possibly dropping

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: On-device Web Speech API

> > So are you OK with adding unprefixing to this intent (or if you prefer, a > new one that this is blocked on)? Yeah, I think that's a great idea! I'm also in favor of tracking usage of the prefixed version with the goal of possibly dropping it entirely in the future. It would be helpful if yo

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: On-device Web Speech API

One more question, it looks like the latest spec has not been published to the gh-pages branch yet. Can you please make sure that your changes are visible here ? API owners (chrishtr, bratell, yoavweiss, vmpstr and me) met and agreed: - It would be h

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: On-device Web Speech API

Thank you Evan. Given the samples and github hits you've shared, I agree that web compat will constrain us from making breaking changes to the APi when we unprefix. That's a shame, but is a known reason why we long ago gave up on prefixes as a safe way to do experimental API development. So are you

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: On-device Web Speech API

> > Have you written web platform tests for it? Have a link? I've added a few so far--WPT coverage for the Web Speech API in general is pretty basic at the moment. I'm planning on adding more comprehensive coverage. Here are the ones relevant to this proposal: https://source.chromium.org/chromium/

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: On-device Web Speech API

On Tue, Jan 7, 2025 at 10:34 AM 'Daniel Clark' via blink-dev < blink-dev@chromium.org> wrote: > Adding to Yoav’s feedback about the spec: > >- It’s implied that installOnDeviceSpeechRecognition() happens >synchronously. Making this a blocking call seems problematic since it could >invo

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: On-device Web Speech API

On 1/7/25 3:49 PM, 'Evan Liu' via blink-dev wrote: As for mitigating privacy and fingerprinting risks, we've been collaborating with the team building the Translator API  feature which also has the ability to download and detect language packs

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: On-device Web Speech API

+1 to Dan's feedback; this needs an async API, likely with a streams design. On Wednesday, January 8, 2025 at 7:33:12 AM UTC-8 Rick Byers wrote: > This is great to see! IMHO there are a bunch of great use-cases for > on-device speech recognition which are likely not suitable for server-based >

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: On-device Web Speech API

This is great to see! IMHO there are a bunch of great use-cases for on-device speech recognition which are likely not suitable for server-based approaches. This is still only exposed

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: On-device Web Speech API

On Tue, Jan 7, 2025 at 9:50 PM Evan Liu wrote: > * Are the resources downloaded partitioned per top-level site? What should >> typical download sizes be? > > This depends on the browser--for Chrome on Windows/Mac/Linux, there's only > one instance of each on-device speech recognition language pac

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: On-device Web Speech API

> > * Are the resources downloaded partitioned per top-level site? What should > typical download sizes be? This depends on the browser--for Chrome on Windows/Mac/Linux, there's only one instance of each on-device speech recognition language pack and each language pack is ~60MB. The spec doesn't n

RE: [EXTERNAL] Re: [blink-dev] Intent to Ship: On-device Web Speech API

Adding to Yoav’s feedback about the spec: * It’s implied that installOnDeviceSpeechRecognition() happens synchronously. Making this a blocking call seems problematic since it could involve a fetch and a download. I’d expect it to return a Promise (https://www.w3.org/TR/design-principles/#pr