gecko-dev/dom/u2f/tests
J.C. Jones dccb7bcf7c Bug 1247124 - Limit FIDO U2F to Secure Contexts r=ttaubert,smaug
Use the [SecureContext] webidl notation to hide the powerful "window.u2f"
feature and its interface when not loaded in a secure context.

MozReview-Commit-ID: 7en8b5ieI85
2017-12-13 17:02:38 -06:00
..
browser
pkijs
README.md
frame_appid_facet.html
frame_appid_facet_insecure.html Bug 1247124 - Limit FIDO U2F to Secure Contexts r=ttaubert,smaug 2017-12-13 17:02:38 -06:00
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_multiple_keys.html
test_no_token.html
test_override_request.html
test_register.html
test_register_sign.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.