Hi Alex,

Yes, I can initiate TAG review. Would it work for you if I initiated one
TAG review-request that referenced all four intents? Or alternatively, four
TAG requests? My own feeling is that a joint explainer might be a bit
confusing, since the four surfaces are not very closely related. I don't
feel strongly about this, however, and I can set up a joint explainer if
you don't think it would lead to confusion.

Full disclosure: There's also a fifth one in the pipeline which I've not
yet sent because the PR
<https://github.com/w3c/mediacapture-screen-share/pull/225> has not
yet been merged.

Thanks,
Elad

On Wed, Jun 1, 2022 at 6:13 PM Alex Russell <slightly...@chromium.org>
wrote:

> Hey Elad,
>
> This is a pretty simple design, and it's great to see the progress here.
> That said, this group of intents (systemAudio, suppressLocalAudioPlayback,
> and selfBrowserSurface) would benefit from a joint explainer with
> considered alternatives outlined. The TAG might not have much to say about
> small changes, but our process asks teams to *at least *send them an FYI
> for non-controversial updates so that they can consider how parts fit
> together in future.
>
> Given that the WebRTC group has a history of trying to skip TAG review, it
> doesn't seem right for this set of features to launch without some
> intentional design review. Can you file a request with them or get several
> of the current and former TAG members (Rossen, David, Alice, myself, or
> Domenic) in the project to review the design directly?
>
> Thanks
>
>
> On Wednesday, June 1, 2022 at 12:35:24 AM UTC-7 Elad Alon wrote:
>
>> I've set my alarm.
>> I'll implicitly assume the same period is intended for the other three
>> intents-to-ship sent at roughly the same time.
>>
>> On Wed, Jun 1, 2022 at 9:29 AM Yoav Weiss <yoavwe...@chromium.org> wrote:
>>
>>> Let's give them 1 more week to respond.
>>>
>>> On Wed, Jun 1, 2022 at 9:21 AM Elad Alon <elada...@google.com> wrote:
>>>
>>>> Okay, will do. (I've also sent a personal email on the day the intent
>>>> went out.)
>>>> When shall I ping this thread if no response is received?
>>>>
>>>> On Wed, Jun 1, 2022 at 8:30 AM Yoav Weiss <yoavwe...@chromium.org>
>>>> wrote:
>>>>
>>>>>
>>>>>
>>>>> On Wednesday, May 25, 2022 at 2:38:53 PM UTC+2 Elad Alon wrote:
>>>>>
>>>>>> Contact emailselada...@chromium.org
>>>>>>
>>>>>> Explainer
>>>>>> https://docs.google.com/document/d/1q3oGy7hLJmdQA4ZK7QG7DnwgtcpL6oB2pqLQJ6MP1tY/edit?usp=sharing
>>>>>>
>>>>>
>>>>>>
>>>>>> Specification
>>>>>> https://github.com/w3c/mediacapture-screen-share/pull/222/files
>>>>>>
>>>>>> Summary
>>>>>>
>>>>>> Hint indicating to the user agent whether the application, upon
>>>>>> calling getDisplayMedia() with {audio: true} or similar, wishes *system
>>>>>> audio* to be offered to the user. (If not - only offer tab-audio.)
>>>>>>
>>>>>>
>>>>>> 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/638) 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/032247.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.
>>>>>>
>>>>>
>>>>> While encouraging, neither counts as a positive position based on
>>>>> https://bit.ly/blink-signals
>>>>> It might be good to give them a few more days to chime in.
>>>>>
>>>>>
>>>>>> *Web developers*: Positive Endorsed by Google Meet.
>>>>>>
>>>>>> Security
>>>>>>
>>>>>> This feature can only be used by Web applications to REDUCE the
>>>>>> amount of private information they obtain from the user. As such, this 
>>>>>> is a
>>>>>> net security gain.
>>>>>>
>>>>>>
>>>>>>
>>>>>> 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 bug
>>>>>> https://bugs.chromium.org/p/chromium/issues/detail?id=1329129
>>>>>>
>>>>>> Estimated milestones
>>>>>>
>>>>>> No milestones specified
>>>>>>
>>>>>>
>>>>>>
>>>>>> Link to entry on the Chrome Platform Status
>>>>>> https://chromestatus.com/feature/4649448880734208
>>>>>>
>>>>>> Links to previous Intent discussionsIntent to prototype:
>>>>>> https://groups.google.com/a/chromium.org/g/blink-dev/c/zUJh3aXAC3k
>>>>>>
>>>>>> 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/CAMO6jDPLm8t5xKe4qX_OL-%2BRitdmad0S0HKBmDXrkYznDkZOWQ%40mail.gmail.com.

Reply via email to