Our current UserGestureIndicator-based code has activation state shared across the renderer. With UserActivationV2, the state becomes frame based, and a child frame is not "activated" through user interaction in its parent frame.
This expected behavior change is causing the following tests to fail:
[Layout tests]
external/wpt/fullscreen/model/move-to-fullscreen-iframe-manual.html
fast/events/open-window-from-another-frame.html
fast/dom/Window/window-postmessage-user-gesture.html
fullscreen/api/element-request-fullscreen-two-iframes.html
[browser_tests]
ClipboardApiTest.HostedAppNoPermission
ContentCapabilitiesTest.ClipboardWrite
---
The list above is not exhaustive, we have to few more failing browser tests to dig into.
Comment 1 by mustaq@chromium.org
, Jan 23 2018