On Wed, Mar 23, 2022 at 7:04 AM Yoav Weiss <yoavwe...@chromium.org> wrote:

> Just to make sure I understand correctly: This request is to extend the OT
> by a single milestone, to enable partners to continue experimenting while
> the I2S
> <https://groups.google.com/a/chromium.org/g/blink-dev/c/eZE9LTJMUlk/m/VcvfTuEyAgAJ>
> is being discussed?
>
> On Monday, March 21, 2022 at 8:57:50 PM UTC+1 Elad Alon wrote:
>
>> Prior to pressing "send" I neglected to add the following clarification
>> over the auto-generated content:
>> TAG was positive: "Thank you for bringing this to our attention, and we
>> are happy to see this proposal move forward."
>> They did suggest a change of name (Region Capture -> Tab Region Capture),
>> but that does not affect the API. This proposal to refine the name will be
>> brought up with the WG.
>>
>> On Monday, March 21, 2022 at 8:43:45 PM UTC+1 Elad Alon wrote:
>>
>>> Contact emailselad...@chromium.org, mfo...@chromium.org,
>>> jop...@chromium.org
>>>
>>> Explainerhttps://github.com/w3c/mediacapture-region/blob/main/README.md
>>>
>>> Specificationhttps://w3c.github.io/mediacapture-region/
>>>
>>> Summary
>>>
>>> We introduce a performant and robust API for cropping a self-capture
>>> video track. (Recall that applications may *already* video-capture the tab
>>> in which the application is run using getDisplayMedia(). Using our new
>>> Region Capture, such an application may now *crop* that track and remove
>>> some content from it; typically before sharing it remotely.)
>>>
>>>
>>> Blink componentBlink
>>> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink>
>>>
>>> TAG reviewhttps://github.com/w3ctag/design-reviews/issues/710
>>>
>>> TAG review statusNot applicable
>>>
>>> Risks
>>>
>>> Interoperability and Compatibility
>>>
>>>
>>> Gecko: No signal (
>>> https://github.com/mozilla/standards-positions/issues/621)
>>>
>>> WebKit: No signal (
>>> https://lists.webkit.org/pipermail/webkit-dev/2022-March/032157.html)
>>>
>>> Web developers: Strongly positive This work saw strong support from Web
>>> developers inside of Google (Meet, Docs, Slides). Public statements of
>>> support coming.
>>>
>>> Other signals:
>>>
>>> Ergonomics
>>>
>>> N/A
>>>
>>> Activation
>>>
>>> Unchallenging to use.
>>>
>>> Security
>>>
>>> This is a mechanism by which an application purposefully strips away
>>> information which it already has access to (via pre-existing mechanisms
>>> such as getDisplayMedia).
>>>
>>>
>>> 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?
>>>
>>>
>>>
>>> Goals for experimentation
>>>
>>> Evaluate the usefulness of the feature and gather Web-developer feedback
>>> about how it may improve.
>>>
>>>
>>> Reason this experiment is being extended
>>>
>>>
>>>    - Continue soliciting feedback from developers while getting ready
>>>    to ship.
>>>    - Partners have invested significantly in this experimental API. Out
>>>    of consideration for them, when we eventually request to ship, we will
>>>    request gapless shipping. This implies extending the experiment up to the
>>>    point of shipping. (Note that an intent-to-ship will also be sent today.)
>>>    - We therefore request extending by the usual 3 milestones - so up
>>>    to and including m104. However, we hope this will be shipped before the
>>>    extended period elapses.
>>>
>>> Oops, missed this bit. Consider my question answered!

>
>>> Debuggability
>>>
>>> -
>>>
>>> Will this feature be supported on all six Blink platforms (Windows, Mac,
>>> Linux, Chrome OS, Android, and Android WebView)?No
>>>
>>> Supported on all desktop platforms, but not on mobile platforms, as the
>>> prerequisite API of getDisplayMedia is currently only available on desktop.
>>>
>>> Is this feature fully tested by web-platform-tests
>>> <https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md>
>>> ?No
>>>
>>> Flag nameRegionCapture
>>>
>>> Tracking bug
>>> https://bugs.chromium.org/p/chromium/issues/detail?id=1247761
>>>
>>> Launch bughttps://bugs.chromium.org/p/chromium/issues/detail?id=1168076
>>>
>>> Estimated milestones
>>> OriginTrial desktop last 101
>>> OriginTrial desktop first 98
>>> Link to entry on the Chrome Platform Status
>>> https://chromestatus.com/feature/5712447794053120
>>>
>>> Links to previous Intent discussionsIntent to prototype:
>>> https://groups.google.com/a/chromium.org/g/blink-dev/c/dib14W1B0Xc
>>> Intent to Experiment:
>>> https://groups.google.com/a/chromium.org/g/blink-dev/c/yFUX0KfuUlo
>>>
>>>
>>> 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/446dc47c-610a-44b6-ba3c-b2640049e70dn%40chromium.org
> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/446dc47c-610a-44b6-ba3c-b2640049e70dn%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/CAL5BFfXWhfyk56B%2Bio6irpwqi%2B9P2q3UOS4rxT8MmmahHKxuWg%40mail.gmail.com.

Reply via email to