rijubrat...@intel.com,
eero.h...@intel.com,
fbea...@google.com
https://github.com/riju/eyeGazeCorrection/blob/main/explainer.md
Some platforms or User Agents may provide built-in support for automatic Eye Gaze Correction, in particular for camera video streams.
Web applications may either want to control the levers which can be a simple ON/OFF or an enhanced version like STARE/ TELEPROMPTER mode or at least be aware that .
This may allow the web application to update its UI or to not apply Eye Gaze Correction on its own.
Eye Contact / Gaze Redirection is a technique designed to help ensure that your eyes are looking at the camera when presenting in a video call.
Camera placement can determine how we are looking in the video but now novel techniques can shift our eyes and create a sense that we are always making eye contact,
which is a powerful social stimulus. That helps to create a sense of connection and engagement with the viewer.
This Eye Gaze Correction API gives developers a choice to use the native platform's API.
https://github.com/w3c/mediacapture-extensions/pull/56
webrtc, AI, camera, studio/
visual effects
None
Pending
None
Gecko: No signal
https://github.com/mozilla/standards-positions/issues/934
Jan-Ivar (Mozilla)
is involved in the discussions.
WebKit: No signal
https://github.com/WebKit/standards-positions/issues/287
Youenn Fablet (Apple) is 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=1506956
No milestones specified
https://chromestatus.com/feature/5140905475964928
This intent message was generated by Chrome Platform Status.