rijubrat...@intel.com, eero.h...@intel.com,
https://github.com/riju/faceFraming/blob/main/explainer.md
Some platforms or User Agents may provide built-in support for automatic continuous framing based on the position of human faces
within the field of view, in particular for camera video streams. Web applications may either want to control or at least be aware that
automatic continuous human face framing is applied at the source level. This may for instance allow the web application to
update its UI or to not apply human face framing on its own.
The Face Framing API makes it possible for web apps to ask the operating system to efficiently apply the automatic face framing
effect to a camera's video feed. This eliminates the costly need for manual application of the effect through machine learning
frameworks such as TensorFlow.js, Mediapipe, or cloud-based solutions, which require processing each video frame individually.
None
Pending
None
Gecko: No signal (https://github.com/mozilla/standards-positions/issues/881) Jan-Ivar (Mozilla)
approved
and merged the spec PR (https://github.com/w3c/mediacapture-extensions/pull/55#pullrequestreview-1365241197)
WebKit: No signal (https://github.com/WebKit/standards-positions/issues/253)
Youenn Fablet (Apple) is co-author
and supportive of this change.
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
No specific DevTools changes are required. This feature is treated like any other JS method.
Yes.
--enable-blink-features=MediaCaptureCameraControl
None
None
False
https://bugs.chromium.org/p/chromium/issues/detail?id=1458341
No milestones specified
https://chromestatus.com/feature/5129939115835392
This intent message was generated by Chrome Platform Status.