search

WICG / gesture-delegation

Gesture Delegation API proposal
Other
7 stars 5 forks source link

Gesture is Chromium-specific jargon; the web-developer facing term is "user activation" #2

Closed domenic closed 6 years ago

domenic commented 7 years ago

To match other platform APIs that expose this concept (such as iframe sandbox), the attribute should be allowuseractivationdelegation.

annevk commented 7 years ago

Maybe just allowuseractivation? That seems more consistent with allowfullscreen and allowpaymentrequest.

domenic commented 7 years ago

The issue is that (as per #4) it's not actually about allowing user activation. It's about allowing delegation of user activation, which in turn allows other features like fullscreen.

Figuring out #4 though is a bit of a blocker, especially with regard to your comment at https://github.com/WICG/gesture-delegation/issues/4#issuecomment-331864409

mustaqahmed commented 7 years ago

@domenic, it seems to me that request #3 handled this issue. In particular, allowedActivationDelegation looks like a what you preferred above. May be we can close this issue?

annevk commented 7 years ago

No, "allowed" is wrong. It needs to be "allow" to be consistent.

jyasskin commented 7 years ago

Well, "allowed"->"allow" is a different issue than "gesture"->"activation", so I've filed it as #6.

annevk commented 7 years ago

That issue fails to capture something else I just noticed, that "user" somehow got dropped, even though as OP points out we already use that in identifiers.

mmoss commented 7 years ago

Has this been implemented yet, and if so which builds can we find it in? I wasn't able to use this in the latest version of Canary, which was surprising, since was referenced by the Autoplay Policy Changes. If this is purely proposal (i.e. not implemented yet), how should someone proceed to test the latest policy changes in Canary (and work around them without this API)?