api.UserActivation - chromium support a non-standard proposal to define ability to query the state of user activation in worker

[skyclouds2001]

What type of issue is this?

Missing compatibility data

What information was incorrect, unhelpful, or incomplete?

The chromium support a proposal to define ability to query the state of user activation in worker, and has implement it in chromium for a long time (bug)

This may includes MessageEvent.userActivation MessageEventInit.userActivation {Window,Worker,MessagePort}.postMessage.includeUserActivation_option

Its explainer is at https://github.com/dtapuska/useractivation and whatwg/html#1983

See the related browser tracker issue https://issues.chromium.org/issues/368730565

What browsers does this problem apply to, if applicable?

Chromium (Chrome, Edge 79+, Opera, Samsung Internet)

What did you expect to see?

and BCD for these features

Did you test this? If so, how?

yes, by viewing the source code and test in browser console

Can you link to any release notes, bugs, pull requests, or MDN pages related to this?

No response

Do you have anything more you want to share?

I didn't not check this in other browsers.

MDN URL

No response

MDN metadata

No response

[skyclouds2001]

full features:

• api.MessageEvent.userActivation
• api.Window.postMessage.options_includeUserActivation_parameter
• api.Worker.postMessage.options_includeUserActivation_parameter
• api.MessagePort.postMessage.options_includeUserActivation_parameter

enabled version:

chromium: M72 (confirmed by reasearches in commits and the bug's milestone, also, it's same to other user activation features)
firefox: none (confirmed by test in browser and check source code)
safari: none (confirmed by test in browser and check source code)

researches:

chromium's support:

• ...
• runtime flag enabled by default at chromium/chromium@998565f, in M72
• usage collect at chromium/chromium@fc46809, in M74
• retire runtime flag at chromium/chromium@0294edd, in M85