Contact emails [email protected]<mailto:[email protected]>, [email protected]<mailto:[email protected]>, [email protected]<mailto:[email protected]>, [email protected]<mailto:[email protected]>
Explainer https://github.com/riju/backgroundBlur/blob/main/explainer.md Specification https://w3c.github.io/mediacapture-extensions/#exposing-mediastreamtrack-source-background-blur-support https://w3c.github.io/mediacapture-extensions/#exposing-change-of-mediastreamtrack-configuration Summary The Background Blur API allows web developers to use the native platform's API for camera background segmentation. As Background Blur has become one of the most used features on video conferencing apps like Teams, Meet, Zoom, and Webex, we want web apps to leverage the same platform APIs without completely relying on ML frameworks like TensorFlow.js, Mediapipe, WASM libraries or cloud-based solutions. Blink component Blink>ImageCapture TAG review https://github.com/w3ctag/design-reviews/issues/826 TAG review status Pending Risks External signals Gecko: Positive (https://github.com/mozilla/standards-positions/issues/658) WebKit: Positive (https://github.com/WebKit/standards-positions/issues/5) Web developers: Positive (https://twitter.com/quicksave2k/status/1638908125385220096) Debuggability No specific DevTools changes are required. This feature is treated like any other JS method. Ongoing technical constraints None. Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, ChromeOS, Android, and Android WebView)? No - Supported on ChromeOS, Windows, and macOS, due to the feature's reliance on platform APIs. Is this feature fully tested by web-platform-tests? Yes. https://wpt.fyi/results/mediacapture-extensions/GUM-backgroundBlur.https.html?label=experimental&label=master&aligned Flag name --enable-blink-features=MediaCaptureBackgroundBlur Requires code in //chrome? No. Tracking bug https://crbug.com/1338665 Estimated milestone We hope to start the Origin Trial sometime during M114 beta. We plan to continue the Origin Trial until at least M117 to give developers time to test the API and provide feedback. Goals for experimentation Large customers like Meet can evaluate this API on a big number of users. We can learn if the API in its present form satisfies the needs of the users, or do we need something more to wow the users. One concrete example would be boolean vs enumeration. Right now, BG Blur only uses a bool which is an ON/OFF switch, but ChromeOS and Windows 11 offer shallow focus also where the blur intensity is more than the present implementation. We wanted to start off with something simple, get feedback and iterate on building something which the majority wants. Link to entry on the Chrome Platform Status https://chromestatus.com/feature/5147589575442432 Links to previous Intent discussions https://groups.google.com/a/chromium.org/g/blink-dev/c/3ke9hgaREwM -- 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/CO1PR11MB5186BD2AC21518C03A5211FDF08B9%40CO1PR11MB5186.namprd11.prod.outlook.com.
