Issue metadata
Sign in to add a comment
|
Suggestion: Require user guesture for permission requests for all new APIs |
||||||||||||||||||||||
Issue descriptionI think on-load permission requests are really bad for UX and would suggest ideally we would deprecate them, but that it is difficult to do without breaking existing sites and implementations. Therefore I propose that all new permission requesting mechanisms and new APIs require a user gesture. We could then show a message in the console for any sites that break this rule pointing them to a guide for how to construct a nice permissions flow. Curious if this has been considered previously - reflecting on our experiences with push I wish we had done this for it. Thanks
,
Apr 22 2016
The Permissions API has a bug for this at https://github.com/w3c/permissions/issues/77. In Web Bluetooth, our users have run into trouble with issue 404161, that Promises block a user-gesture chain. Otherwise, I think we're doing well.
,
Jul 11 2016
,
Nov 22 2016
,
Nov 29 2016
,
Nov 10 2017
,
Feb 18 2018
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by palmer@chromium.org
, Apr 22 2016