Meta bug for tests that should fail with UAv2 |
|
Issue descriptionWith User Activation v2 model change (vs old UGI-based bahavior), we expect some existing tests to behave differently or even fail. Most (all?) of these diffs are caused by these UAv2 changes: - Clicking on a frame doesn't activate any of its child frames. - Transient user activation is not stack-scoped. - Workarounds/hacks added for the old model are no longer applicable. This bug depends on (blocked by) all those tests. We need to either rewrite them with modified expectations or nuke them after UAV2 ships.
,
Nov 27
Here is another: external/wpt/fullscreen/api/element-ready-check-containing-iframe-manual.html
,
Nov 27
Here are a few browser tests that would need cleanup: https://cs.chromium.org/search/?q=file:test%5C.cc$+kUserActivationV2 |
|
►
Sign in to add a comment |
|
Comment 1 by mustaq@chromium.org
, Nov 27