Regarding interop support, this change was discussed at TPAC 2024 this year
and was supported by Eric Carlson from Apple and Paul Adenot from Mozilla
among others. I've submitted requests for formal permissions from Mozilla
<https://github.com/mozilla/standards-positions/issues/1149> and WebKit
<https://github.com/WebKit/standards-positions/issues/438>.

I've flipped all of the chromestatus review bits as well.

Thanks!
Evan

On Wed, Dec 18, 2024 at 7:26 AM Yoav Weiss (@Shopify) <
yoavwe...@chromium.org> wrote:

> You also probably want to flip the relevant chromestatus review bits (for
> security, privacy, etc).
>
> On Wednesday, December 18, 2024 at 2:27:42 AM UTC+1 dan...@microsoft.com
> wrote:
>
>> The links supporting the browser Gecko and WebKit signals do not seem
>> strongly indicative of a current positive position.
>> https://github.com/WICG/speech-api/pull/118 from 2014 was resolved
>> WONTFIX and skimming through https://github.com/WICG/speech-api/issues/66
>> the issue did not appear to reach any strong resolution. I think it would
>> make sense to request formal positions <https://bit.ly/blink-signals> to
>> try to get a clearer picture.
>>
>>
>>
>> -- Dan Clark
>>
>>
>>
>> *From:* blink-dev@chromium.org <blink-dev@chromium.org> *On Behalf Of *
>> Chromestatus
>> *Sent:* Tuesday, December 17, 2024 4:28 PM
>> *To:* blink-dev@chromium.org
>> *Cc:* ev...@google.com
>> *Subject:* [EXTERNAL] [blink-dev] Intent to Ship: Add MediaStreamTrack
>> support to the Web Speech API
>>
>>
>> Contact emails
>>
>> ev...@google.com
>> Explainer
>>
>> https://github.com/WICG/speech-api/pull/118
>> Specification
>>
>> https://wicg.github.io/speech-api
>> Design docs
>>
>>
>>
>> https://docs.google.com/document/d/1LHGtO6A-U4OFQpG9LXUf1_4Elerpv1rncNCbHnmA7zY/edit?usp=sharing
>> Summary
>>
>> Add MediaStreamTrack support to the Web Speech API. The Web Speech API is
>> a web standard API that allows developers to incorporate speech recognition
>> and synthesis into their web pages. Currently, the Web Speech API uses the
>> user's default microphone as the audio input. MediaStreamTrack support
>> allows websites to use the Web Speech API to caption other sources of audio
>> including remote audio tracks.
>>
>>
>> Blink component
>>
>> Blink>Speech
>> <https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3ESpeech%22>
>> Search tags
>>
>> speech <http:///features#tags:speech>, recognition
>> <http:///features#tags:recognition>
>> TAG review
>>
>> None
>> TAG review status
>>
>> Not applicable
>> Risks
>>
>>
>> Interoperability and Compatibility
>>
>> None
>>
>>
>>
>> *Gecko*: Positive (https://github.com/WICG/speech-api/issues/66) Similar
>> changes proposed by Firefox in 2019
>>
>> *WebKit*: Positive (https://www.w3.org/Bugs/Public/show_bug.cgi?id=26336)
>> Similar changes proposed by Safari in 2014
>>
>> *Web developers*: Positive (
>> https://stackoverflow.com/questions/67351357/web-speech-recognition-on-mediastream)
>> Feature requested by web developers
>>
>> *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
>>
>>
>> Will this feature be supported on all six Blink platforms (Windows, Mac,
>> Linux, ChromeOS, Android, and Android WebView)?
>>
>> No
>>
>> Initially supported on Windows, Mac, and Linux with ChromeOS support to
>> follow.
>>
>>
>> Is this feature fully tested by web-platform-tests
>> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>
>> ?
>>
>> No
>> Flag name on about://flags
>>
>> None
>> Finch feature name
>>
>> MediaStreamTrackWebSpeech
>> Requires code in //chrome?
>>
>> False
>> Estimated milestones
>>
>> Shipping on desktop
>>
>> 133
>>
>>
>> Anticipated spec changes
>>
>> *Open questions about a feature may be a source of future web compat or
>> interop issues. Please list open issues (e.g. links to known github issues
>> in the project for the feature specification) whose resolution may
>> introduce web compat/interop risk (e.g., changing to naming or structure of
>> the API in a non-backward-compatible way).*
>>
>> Spec changes will be made to the Web Speech API spec after the spec repo
>> migrates over to the Audio Community Group. Tentative spec PR changes:
>> https://github.com/WICG/speech-api/pull/118
>> Link to entry on the Chrome Platform Status
>>
>> https://chromestatus.com/feature/5178378197139456?gate=5091779878846464
>>
>> 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/6762170b.2b0a0220.38516f.0183.GAE%40google.com
>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/6762170b.2b0a0220.38516f.0183.GAE%40google.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/CAOVsCZkkW%2BqYqFPjJxxtmd38tttSJ%3D0KQxhgLH4FYVGMZiwZ1A%40mail.gmail.com.

Reply via email to