gecko-dev/dom/u2f/tests
Michelle Goossens c7d34da2f9 Bug 1723574 - Enable mochitest-browser-chrome tests that no longer fail r=jmaher
Differential Revision: https://phabricator.services.mozilla.com/D123247
2021-08-23 12:45:31 +00:00
..
browser Bug 1723574 - Enable mochitest-browser-chrome tests that no longer fail r=jmaher 2021-08-23 12:45:31 +00:00
pkijs
.eslintrc.js
README.md
frame_appid_facet.html
frame_appid_facet_insecure.html
frame_appid_facet_subdomain.html
frame_multiple_keys.html
frame_no_token.html
frame_override_request.html
frame_register.html
frame_register_sign.html
frame_utils.js
mochitest.ini
test_appid_facet.html
test_appid_facet_insecure.html
test_appid_facet_subdomain.html
test_bind.html
test_multiple_keys.html
test_no_token.html
test_override_request.html
test_polyfill_interaction.html
test_register.html
test_register_sign.html
test_u2f_replaceable.html
test_util_methods.html
u2futil.js

README.md

Note:

While conceptually similar to the tests for Web Authentication (dom/webauthn), the tests for U2F require an iframe while window.u2f remains hidden behind a preference, though WebAuthn does not. The reason is that the window object doesn't mutate upon a call by SpecialPowers.setPrefEnv() the way that the navigator objects do, rather you have to load a different page with a different window object for the preference change to be honored.