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 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 <dome...@chromium.org> > wrote: > >> 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 events: audiostart, audioend, start, end, soundstart, >> soundend, speechstart, speechend, result, nomatch >> >> >> Thank you! >> >> On Tuesday, April 22, 2025 at 7:22:53 AM UTC+9 ev...@google.com wrote: >> >>> 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> wrote: >>> >>>> 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 AbortSignal parameter to the download/install function >>>> >>>> For the first one I see that you have >>>> https://github.com/WebAudio/web-speech-api/pull/150. >>>> For the other two, are those changes you plan to make prior to >>>> shipping? The second one in particular seems like it'd be breaking if done >>>> afterwards. >>>> >>>> -- Dan >>>> On Friday, April 18, 2025 at 11:31:50 AM UTC-7 ev...@google.com wrote: >>>> >>>>> 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 particular reason to unprefix before >>>>>> shipping on-device, is there? >>>>> >>>>> Also to answer your question, Rick, I don't think there's any reason >>>>> to unprefix before shipping on-device, so we might as well lump it >>>>> together >>>>> as a bundle :). >>>>> >>>>> Thanks! >>>>> Evan >>>>> >>>>> On Wed, Apr 16, 2025 at 10:54 AM Brian Kardell <bkar...@gmail.com> >>>>> wrote: >>>>> >>>>>> 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 Evan Liu <ev...@google.com> 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 < >>>>>>>> jyas...@chromium.org> wrote: >>>>>>>> >>>>>>>>> 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 <ev...@google.com> 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)? >>>>>>>>>> >>>>>>>>>> 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 >>>>>>>>>> unprefixing >>>>>>>>>>> alone >>>>>>>>>>> <https://chromium-review.googlesource.com/c/chromium/src/+/6422562> >>>>>>>>>>> now, >>>>>>>>>>> since you already proved to us that the unprefixed API is not an >>>>>>>>>>> opportunity to make any breaking API changes. Do you prefer to >>>>>>>>>>> decouple >>>>>>>>>>> that, or just wait and get the whole bundle approved to ship >>>>>>>>>>> together? >>>>>>>>>>> >>>>>>>>>> Either is fine with me! Would decoupling just be a matter of >>>>>>>>>> making the changes, or would I need to create a separate Chrome >>>>>>>>>> Status >>>>>>>>>> entry, get position statements, all of the approvals, etc.? If it's >>>>>>>>>> the >>>>>>>>>> former, we might as well make the change now. Otherwise it might >>>>>>>>>> just be >>>>>>>>>> easier to bundle everything together. >>>>>>>>>> >>>>>>>>> >>>>>>> I'm OK with just shipping the unprefixing under this same intent >>>>>>> without the extra paperwork, but also it's a bit simpler if we just >>>>>>> keep it >>>>>>> all lumped together as a bundle. I don't think there's any particular >>>>>>> reason to unprefix before shipping on-device, is there? >>>>>>> >>>>>>> >>>>>>>> >>>>>>>>>> Thanks, >>>>>>>>>> Evan >>>>>>>>>> >>>>>>>>>> On Fri, Apr 4, 2025 at 6:51 AM Thomas Steiner <to...@google.com> >>>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>>> 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 years >>>>>>>>>>> from now >>>>>>>>>>> and wonder… >>>>>>>>>>> >>>>>>>>>> >>>>>>> Whoops, yes of course - thank you :-). >>>>>>> >>>>>>> >>>>>>>> >>>>>>>>>>> >>>>>>>>>> -- >>>> You received this message because you are subscribed to a topic in the >>>> Google Groups "blink-dev" group. >>>> To unsubscribe from this topic, visit >>>> https://groups.google.com/a/chromium.org/d/topic/blink-dev/VNOok2dbmHM/unsubscribe >>>> . >>>> To unsubscribe from this group and all its topics, 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/3deb7274-8a70-4b28-a60a-02d76d22ba14n%40chromium.org >>>> >>>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/3deb7274-8a70-4b28-a60a-02d76d22ba14n%40chromium.org?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/6f99a731-efd8-4351-861f-73afbecd3b9cn%40chromium.org.
