gecko-dev/dom/u2f/tests/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.
Bug 1333592 - Fix a regression with U2F sign() called with multiple keys r=keeler Add a test that U2F supports signing with multiple keys. Reorder the WaitGroupDone calls to ensure they always fire, even if there are multiple actions in flight. Also, change the status lanbda captures to capture by reference, and disable the copy constructor that would let the by-value work. Interestingly, the compiler is choosing by-reference by default -- at least logs show that the behavior is correct without this change, but still - this is the right thing to do. Updated: Fix the unit tests and write a README that explains why they have to use an iframe, while WebAuthn tests do not. MozReview-Commit-ID: AqSyxU5N4yu --HG-- extra : rebase_source : b8f18973891ba63ac364203dece65a0689f46ee5 2017-01-27 01:18:50 +03:00			`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.