search

WICG / gesture-delegation

Gesture Delegation API proposal
Other
7 stars 5 forks source link

delegatestickyuseractivation is a really awkward name #12

Open othermaciej opened 6 years ago

othermaciej commented 6 years ago

delegatestickyuseractivation / delegateStickyUserActivation is a long an awkward name. Also, it assumes Chrome's specific model of sticky user activation, which is not necessarily how it works in other UAs. Safari does not have any permission that is sticky within eTLD+1.

How about: sharepermission/sharePermission?

jyasskin commented 6 years ago

"sharePermission" would be a different meaning, but I also prefer that other meaning (#4).

mounirlamouri commented 6 years ago

sharePermission and "that other meaning" would be way too close to Feature Policy.

@othermaciej I'm happy to discuss a solution that could be Safari-Chrome compatible here.

othermaciej commented 6 years ago

For most things with a user gesture requirement, the requirement is not "sticky". The concept of "gesture delegation" is just plain weird. This spec is not delegating a specific user gesture, it's granting the permission that comes from a user gesture. Ideally it shouldn't be completely separate from a mechanism that delegates permission that is granted in a different way, since we don't want to set UI requirements on how browsers allow things.