Issue metadata
Sign in to add a comment
|
New "user gesture required" error inside Promise chain when requesting permission during click
Reported by
peter.m....@gmail.com,
Aug 6
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36 Steps to reproduce the problem: 1. Install the extension here: https://github.com/mrcoles/test-chrome-extension-per-promise-chrome-69 2. In any window activate the extension 3. Click the link in the popup What is the expected behavior? The extension starts a very simple Promise chain and then requests the "downloads" permission. This should successfully request the permission, as the request is within the user gesture (even if it’s in a Promise) Popup text should update with "Successfully requested and got result [true|false]". What went wrong? A runtime error is encountered during the permissions request of: > This function must be called during a user gesture permission Fails in: * Chrome 70.0.3514.0, Mac OS X 10.13.5 * Chrome 69.0.3497, Mac OS X 10.13.4 Works in: * 67.0.3396.99, Mac OS X 10.13.5 Did this work before? N/A Does this work in other browsers? N/A Chrome version: 70.0.3514.0 Channel: canary OS Version: OS X 10.13.5 Flash Version: This is not a dupe of https://bugs.chromium.org/p/chromium/issues/detail?id=735097 but seems like this type of issue has appeared in the past.
,
Aug 7
,
Aug 8
This also works in Chrome 68.0.3440.84 on Mac OS X 10.13.5 It appears this is first introduced in v69.
,
Aug 9
peter.m.coles@ Thanks for the issue/ Able to reproduce this issue on Windows 10, Mac OS 10.13.3 on the latest Dev 70.0.3514.0 and canary 70.0.3517.0 , but the issue is not reproducible on the equivalent chrome builds. Note: Issue is not observed on Ubuntu 17.10. Attached are the screen shots for reference. As the issue is not reproducible on the equivalent chrome builds, unable to provide the bisect information. Hence marking this as Untriaged for further updates from Dev. Thanks..
,
Aug 9
OK, given Chrome 69 is scheduled for Sep 4 (https://www.chromestatus.com/features/schedule), do you think this will be reviewed and figured out by then? If it goes live, it will break my extension. Cheers, Peter
,
Aug 17
Can you check if this reproduces with chrome://flags/#user-activation-v2 disabled?
,
Aug 17
@6 - confirmed, it *does* work as before with user-activation-v2 disabled.
,
Aug 17
(prior comment, tested on Mac OSX 10.13.5 running Chrome Version 70.0.3525.0 (Official Build) canary (64-bit))
,
Aug 17
Thanks! User Activation V2 is an experiment that's being run, and is currently only enabled on Canary/Dev populations (I believe), so there shouldn't be risk of stable breakage. mustaq@, passing this to you (though likely it should just be duped into 860509 as well?). Separately, it looks like there's a number of these cropping up - do you have an ETA on a fix?
,
Aug 20
Correct: this is exposed through a Canary/Dev finch trial, doesn't risk stable yet. Merging to the other bug.
,
Aug 20
I couldn't repro it on Chrome beta (69.0.3497.42) on Linux. I had all flags set to default except UAv2=enabled. peter.m.coles@gmail.com: what am I missing here?
,
Aug 20
Nm about #c11: I missed the --enable-features=NativeCrxBindings flag. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by erikc...@chromium.org
, Aug 6