https://github.com/riju/backgroundBlur/blob/main/explainer.md#background-segmentation-mask-api
https://github.com/w3c/mediacapture-extensions/pull/142
The Background Segmentation/Mask API allows web developers to use the native platform's API for camera, leveraging on-device AI models for background segmentation. Today, on Windows/Apple, this can leverage NPU (Neural Processing Units) and bring power and performance gains. This extends our previously proposed Background Blur API [1] with some implementation difference [2] –
In many cases, it might be important to have access to the original camera feed [3]. Green Screen, Background Replacement (with
an Image) and many other use cases can be enabled [4] using this feature via Canvas and WebGPU/GL pipeline. There is still an ongoing discussion about how Mask data is best provided
[5].
[1]
https://developer.chrome.com/blog/background-blur/
[2]
https://github.com/riju/backgroundBlur/blob/main/explainer.md#blur-vs-mask
[3]
https://github.com/w3c/mediacapture-extensions/issues/118#issuecomment-1772204182
[4]
https://github.com/riju/backgroundBlur/blob/main/explainer.md#demo
A vast majority of communication these days happens on our client devices and features like Blur, Background Replacement, Green Screen have become table stakes. This Background Segmentation-Mask API gives developers a choice to use the native platform's API and leverage the on-device AI models already present in the platform.
https://github.com/w3c/mediacapture-extensions/pull/142
None
Pending
None
Gecko: No signal.
https://github.com/mozilla/standards-positions/issues/1041
WebKit: No signal.
https://github.com/WebKit/standards-positions/issues/364
Web developers: No signals
Other signals:
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
None
None
No
None
None
None
False
No milestones specified
https://chromestatus.com/feature/5187283610501120
This intent message was generated by Chrome Platform Status.