P.S: Requesting to ship gaplessly. On Monday, March 21, 2022 at 9:13:30 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 > 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. > > Risks > > Interoperability and Compatibility > > Remaining open issues with Mozilla and Apple: > > > - The name "CropTarget" - see > https://github.com/w3c/mediacapture-region/issues/18. No alternative > has yet been presented which garnered more support than "CropTarget". This > seems unlikely to change. > - Whether produceCropTarget should return a Promise<CropTarget> or a > CropTarget - see https://github.com/w3c/mediacapture-region/issues/17. > In internal discussions we have consensus that returning a Promise is > preferrable. However, if the WG settles on returning a CropTarget > directly, > a migration plan would be needed to ensure Web applications are not > broken. > This would be easier if such a change is either not made at all, or is > made > in concert with the next bullet-point. > - API surface of produceCropTarget - see > https://github.com/w3c/mediacapture-region/issues/11. We want > MediaDevices.produceCropTarget(), whereas Apple wants > Element.produceCropTarget or possibly Element.cropTarget(). Should the WG > settle on Apple's current preference, migration would be very easy, as we > can first expose on the new surface *in addition* and then deprecate the > old surface gradually. Moreover, such a migration would actually have the > potential of making a (Promise<CropTarget> -> CropTarget) migration > simpler, should such a change also be adopted by the WG. > > Other topics under discussion mostly deal with changes to spec-language, > and will not affect the shipped API. Exception - serializability, but that > wouldn't break Web-apps (since it's mostly opaque to the application, which > would typically only postMessage the CropTarget and use it on the other > side). > > *Gecko:* No signal ( > https://github.com/mozilla/standards-positions/issues/621) See above > clarification about remaining open issues under discussion. > > *WebKit:* No signal ( > https://lists.webkit.org/pipermail/webkit-dev/2022-March/032157.html) See > above clarification about remaining open issues under discussion. > > *Web developers:* Strongly positive This work saw strong support from Web > developers inside of Google (Meet, Docs, Slides). > > 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 > > N/A > > > > Debuggability > > - > > 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 bughttps://bugs.chromium.org/p/chromium/issues/detail?id=1247761 > > Launch bughttps://bugs.chromium.org/p/chromium/issues/detail?id=1168076 > > Sample linkshttps://w3c.github.io/mediacapture-region/demo/ > > 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 > Intent to Extend Experiment: > https://groups.google.com/a/chromium.org/g/blink-dev/c/ZqndGb9e1wM > > > 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/4ecf2f16-6e7d-4775-8b67-2075a94298a6n%40chromium.org.
