Thanks. I've set myself a reminder to ping this thread in one week, as
suggested on the other intent thread.

On Wed, Jun 1, 2022 at 8:42 AM Yoav Weiss <[email protected]> wrote:

>
>
> On Wednesday, May 25, 2022 at 2:47:50 PM UTC+2 Elad Alon wrote:
>
>> Contact [email protected]
>>
>> Explainer
>> https://docs.google.com/document/d/1uI51R4YfFQtfiDTw1KfnLqzIu45OgxhYoUT7khlhmwQ/edit?usp=sharing
>>
>> Specification
>> https://github.com/w3c/mediacapture-screen-share/pull/186/files
>>
>> Summary
>>
>> When getDisplayMedia() is called, the browser offers the user a choice of
>> display surfaces - tabs, windows and monitors. Using the displaySurface
>> constraint, the Web application may now hint to the browser if it prefers
>> that a certain surface type be more prominently offered to the user.
>>
>>
>> Blink componentBlink
>> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink>
>>
>> TAG reviewN/A. This is just an addition of a single flag to an existing
>> dictionary, following well-known patterns.
>>
>> TAG review statusNot applicable
>>
>> Risks
>>
>>
>> Interoperability and Compatibility
>>
>> *Gecko*: Positive (
>> https://github.com/mozilla/standards-positions/issues/642) Jan-Ivar
>> Bruaroey from Mozilla, and Youenn Fablet from Apple, have both collaborated
>> with us closely in shaping this PR. They have then approved merging this PR
>> into w3c/mediacapture-screen-share. This is implicit support, so I'd
>> consider it POSITIVE even though, as of the time of this writing, the
>> official request for position has not yet been answered.
>>
>> *WebKit*: Positive (
>> https://lists.webkit.org/pipermail/webkit-dev/2022-May/032253.html)
>> Jan-Ivar Bruaroey from Mozilla, and Youenn Fablet from Apple, have both
>> collaborated with us closely in shaping this PR. They have then approved
>> merging this PR into w3c/mediacapture-screen-share. This is implicit
>> support, so I'd consider it POSITIVE even though, as of the time of this
>> writing, the official request for position has not yet been answered.
>>
>
> Similar to other intents, this doesn't count as an official positive
> signal. Let's wait a few days to see if one emerges.
>
>
>>
>> *Web developers*: Positive See Appendix I of the internal design doc:
>> https://docs.google.com/document/d/1U_aNptMZuYFuFWu7leq43V3hqOQ9zMEumG3x413q2pY/edit#heading=h.693jj8mh4gkw
>>
>> *Other signals*:
>>
>> WebView application risks
>>
>> N/A
>>
>>
>>
>> Debuggability
>>
>> N/A
>>
>>
>> Will this feature be supported on all six Blink platforms (Windows, Mac,
>> Linux, Chrome OS, Android, and Android WebView)?No
>>
>> Supported on all platforms that support getDisplayMedia. Namely, all
>> desktop platforms.
>>
>>
>> Is this feature fully tested by web-platform-tests
>> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>
>> ?No
>>
>> Tracking bughttps://bugs.chromium.org/p/chromium/issues/detail?id=1224912
>>
>> Estimated milestones
>>
>> No milestones specified
>>
>>
>> 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).
>>
>>
>> Link to entry on the Chrome Platform Status
>> https://chromestatus.com/feature/5186392840732672
>>
>> Links to previous Intent discussionsIntent to prototype:
>> https://groups.google.com/a/chromium.org/g/blink-dev/c/bVVEn-TOTYs
>>
>> 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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAMO6jDPv1P9YEEKwt8pTeqSU0wT%2BdyY%2BkwyagovrtFT00c--FQ%40mail.gmail.com.

Reply via email to