Intent to Remove: Calling getDisplayMedia() without user activation

Skip to first unread message

François Beaufort

Dec 19, 2022, 5:53:26 AM12/19/22
to blink-dev

Contact emails



Allowing getDisplayMedia() to be triggered without a user activation could be abused by malicious websites. To protect users, the spec was changed[1] to require user activation, and we are now following through in the Chromium implementation.


Blink component


TAG review

N/A - enforcement of feature from an already-reviewed specification

TAG review status

Not applicable


Interoperability and Compatibility

Firefox and Safari's implementation already require user activation for calling getDisplayMedia().

As websites already handle getDisplayMedia() returned promise rejection for other cases such as user cancelling the browser prompt, I believe there’s no compatibility risk.

We still added[1] a UseCounter[2] to track use of this feature and noted near zero usage.



Gecko: Shipped/Shipping (

WebKit: Shipped/Shipping (

Web developers: No signals

Other signals:


Once the support is removed, calling getDisplayMedia() will throw an InvalidStateError with a clear error message.

Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?

No - Supported on all Desktop platforms.

Is this feature fully tested by web-platform-tests?

Yes -

Requires code in //chrome?


Tracking bug

Estimated milestones


Link to entry on the Chrome Platform Status

Mike Taylor

Dec 19, 2022, 10:41:15 AM12/19/22
to François Beaufort, blink-dev
LGTM1 - aligning with other browsers on this (and the spec!) is good. 0.0002% is indeed low.
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
To view this discussion on the web visit

Rick Byers

Dec 19, 2022, 12:16:26 PM12/19/22
to Mike Taylor, François Beaufort, blink-dev

On Mon, Dec 19, 2022 at 10:41 AM Mike Taylor <> wrote:
LGTM1 - aligning with other browsers on this (and the spec!) is good. 0.0002% is indeed low.

I'll also note that it's <1% the usage of getDisplayMedia, so even though this is a relatively niche feature, the vast majority of the usage should be unimpacted by this change.

Daniel Bratell

Dec 21, 2022, 11:49:52 AM12/21/22
to Rick Byers, Mike Taylor, François Beaufort, blink-dev
Reply all
Reply to author
0 new messages