Contact emails
Explainer
N/A
Design doc/Spec
Specification: https://w3c.github.io/mediacapture-screen-share/
In the process of requesting a tag review.
Summary
Chrome has long supported screen capture (used for videoconferencing screenshare and remote desktop) through a proprietary API that can only be enabled by extensions. The standard API is defined in the screen capture specification.
We intend to add the standard functionality, and eventually remove the older, non-standard API.
Motivation
The screenshare functionality in Chrome has proved popular with videoconferencing service vendors, and is essential to other applications such as Chrome Remote Desktop.
The standardized version has been shipped by other vendors, and there is a desire in the community to have only one API of this type; the need to use an extension to enable the feature is also seen as a drawback for the Chrome non-standard version.
Risks
Interoperability and Compatibility
Describe the degree of interoperability and compatibility risk. For a new feature, the main risk is that it fails to become an interoperable part of the web platform if other browsers do not implement it. For a removal, please review our principles of web compatibility.
Edge: Shipped
Firefox: Shipped (with deviations; tracking bug)
Safari: Positive
Web developers: Positive
Ergonomics
This feature will be commonly used with WebRTC for sharing a desktop or window with others.
Activation
Polyfill on top of the existing functionality may be possible, but still requires using an extension for enabling. The API is very similar to the old one, so most apps should have an easy time switching.
Debuggability
No special considerations.
Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?
Yes. The differing capabilities of the different platforms mean that we can’t be sure to release all of them a the same time.
Is this feature fully tested by web-platform-tests?
No. Tests will be added.
Link to entry on the feature dashboard
https://www.chromestatus.com/feature/6744724455030784
Requesting approval to ship?
No.
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOqqYVFUBDpCw0he12HADkSy6qOdFwbV7EdoXvZzn%2BxBa8bnFg%40mail.gmail.com.
This is great news. I really hope system audio is also enabled as it's critical for sharing media clips
--
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+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/6e9d9fbb-83d5-47ba-a27c-a6a6368ec6cd%40chromium.org.
I really hope Firefox aligns their implementation soon... It implements it using getUserMedia instead of getDisplayMedia.☆PhistucK
On Thu, Jun 14, 2018 at 10:14 PM <jahanze...@gmail.com> wrote:
This is great news. I really hope system audio is also enabled as it's critical for sharing media clips
--
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+unsubscribe@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/e40debc6-e698-4292-a2c5-9df1e275d03f%40chromium.org.