Hi Alex,

We've been having trouble finishing up the engineering work, hence the
delay.  I'm trying to make some workflow adjustments now.

Best,
Michael

On Tue, Oct 17, 2023 at 2:30 PM Alex Russell <slightly...@chromium.org>
wrote:

> What's the rationale for this change? Is it documented anywhere? I don't
> see an Explainer linked.
>
> On Tue, Oct 17, 2023, 2:11 PM 'Ajay Rahatekar' via blink-dev <
> blink-dev@chromium.org> wrote:
>
>> This feature is now planned to ship in M121.
>>
>> On Tuesday, July 18, 2023 at 12:59:23 PM UTC-7 Ajay Rahatekar wrote:
>>
>>> This feature is planned to ship in M118.
>>>
>>> On Thursday, April 13, 2023 at 10:56:40 AM UTC-7 Ajay Rahatekar wrote:
>>>
>>>> A correction. The permission prompt will not be released on Webview at
>>>> this time. This is planned for to be revisited later.
>>>>
>>>> On Wednesday, April 5, 2023 at 4:54:20 PM UTC-7 Ajay Rahatekar wrote:
>>>>
>>>>> Contact emails
>>>>>
>>>>> mjwi...@chromium.org, sinaf...@chromium.org, hong...@chromium.org
>>>>>
>>>>> Specification
>>>>>
>>>>> https://www.w3.org/TR/webmidi/#requestmidiaccess
>>>>>
>>>>> Summary
>>>>>
>>>>> This change will require users to grant permission before they can use
>>>>> the Web MIDI API. Currently, users must explicitly grant permission to use
>>>>> SysEx messages with the Web MIDI API. With this change, users will need to
>>>>> grant a single permission to use the Web MIDI API and SysEx support. Both
>>>>> permissions will be requested in a bundled permission prompt.
>>>>>
>>>>> Blink component
>>>>>
>>>>> Blink>WebMIDI
>>>>> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EWebMIDI>
>>>>>
>>>>> Search tags
>>>>>
>>>>> MIDI <https://chromestatus.com/features#tags:MIDI>, SysEx
>>>>>
>>>>> Risks
>>>>>
>>>>> Firefox already has a permissions prompt on Web MIDI API. We are
>>>>> working with known partners and plan on socializing this Chromium change.
>>>>>
>>>>> Will this feature be supported on all six Blink platforms (Windows,
>>>>> Mac, Linux, Chrome OS, Android, and Android WebView)?
>>>>>
>>>>> Yes
>>>>>
>>>>> Is this feature fully tested by web-platform-tests
>>>>> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>
>>>>> ?
>>>>>
>>>>> No
>>>>>
>>>>> Requires code in //chrome?
>>>>>
>>>>> False
>>>>>
>>>>> Tracking bug
>>>>>
>>>>> https://bugs.chromium.org/p/chromium/issues/detail?id=1420307
>>>>>
>>>>> Estimated milestones
>>>>>
>>>>> We hope to ship this in Q2 2023.
>>>>>
>>>>>
>>>>> 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).
>>>>>
>>>>> None
>>>>>
>>>>>
>>>>> Link to entry on the Chrome Platform Status
>>>>>
>>>>> https://chromestatus.com/feature/5087054662205440
>>>>>
>>>>> 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 on the web visit
>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/cac6d789-cb16-4a4d-b0e2-448acfca2f6an%40chromium.org
>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/cac6d789-cb16-4a4d-b0e2-448acfca2f6an%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 on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CA%2BuAeqTPZ2ydsS1kWdeCKV6DyquMbfUAbmrMu%3D%2B43KQqYmSEBg%40mail.gmail.com.

Reply via email to