diff options
Diffstat (limited to 'testing/web-platform/meta/close-watcher/user-activation-shared.html.ini')
-rw-r--r-- | testing/web-platform/meta/close-watcher/user-activation-shared.html.ini | 70 |
1 files changed, 70 insertions, 0 deletions
diff --git a/testing/web-platform/meta/close-watcher/user-activation-shared.html.ini b/testing/web-platform/meta/close-watcher/user-activation-shared.html.ini new file mode 100644 index 0000000000..656d9daf19 --- /dev/null +++ b/testing/web-platform/meta/close-watcher/user-activation-shared.html.ini @@ -0,0 +1,70 @@ +[user-activation-shared.html?CloseWatcher] + [Close watchers created without user activation, but close()d via user activation, do not fire cancel] + expected: FAIL + + [Close watchers created without user activation, but closed via a close request after user activation, fires cancel] + expected: FAIL + + [Close watchers created without user activation, but closed via a close request after user activation, fires cancel, which can be preventDefault()ed] + expected: FAIL + + [Multiple close watchers created without user activation close together (with no cancel)] + expected: FAIL + + [Creating a close watcher from user activation keeps it separate from the free close watcher, but they don't fire cancel] + expected: FAIL + + [Creating a close watcher from user activation, and closing close watchers with a close request after user activation, fires cancel] + expected: FAIL + + [Multiple close watchers created with user activation close in reverse order] + expected: FAIL + + [3 user activations let you have 3 + 1 = 4 ungrouped close watchers/0 cancel events] + expected: FAIL + + [closing the free close watcher via a close request allows a new free one to be created without user activation, and it receives a second close request] + expected: FAIL + + [The second watcher can be the free watcher, if the first is created with user activation] + expected: FAIL + + [The third watcher can be the free watcher, if the first two are created with user activation] + expected: FAIL + + [destroy()ing the free close watcher allows a new free one to be created without user activation, and it receives the close request] + expected: FAIL + + +[user-activation-shared.html?dialog] + [Close watchers created without user activation, but close()d via user activation, do not fire cancel] + expected: + if (os == "win") and debug and (processor == "x86_64") and swgl: [FAIL, PASS] + if (os == "win") and debug and (processor == "x86"): [FAIL, PASS] + if (os == "linux") and not swgl: [FAIL, PASS] + if (os == "android") and not swgl: [FAIL, PASS] + FAIL + + [Multiple close watchers created without user activation close together (with no cancel)] + expected: FAIL + + [Creating a close watcher from user activation keeps it separate from the free close watcher, but they don't fire cancel] + expected: FAIL + + [Multiple close watchers created with user activation close in reverse order] + expected: FAIL + + [3 user activations let you have 3 + 1 = 4 ungrouped close watchers/0 cancel events] + expected: FAIL + + [closing the free close watcher via a close request allows a new free one to be created without user activation, and it receives a second close request] + expected: FAIL + + [The second watcher can be the free watcher, if the first is created with user activation] + expected: FAIL + + [The third watcher can be the free watcher, if the first two are created with user activation] + expected: FAIL + + [destroy()ing the free close watcher allows a new free one to be created without user activation, and it receives the close request] + expected: FAIL |