Closed Bug 1685359 Opened 4 years ago Closed 4 years ago

Fix failing DOM:Web Authentication tests with cross-origin


(Core :: DOM: Web Authentication, defect)




Fission Milestone M7


(Reporter: neha, Assigned: rmf)


(Blocks 1 open bug)



(1 obsolete file)

The following tests fail with cross-origin enabled AND Fission disabled (they pass for Fission AND xorigin enabled). This is very suspicious and most likely, the test (or the feature itself) needs to be fixed for cross-origin behavior. It's also possible that by design, these tests (and features) are not expected to work cross-origin, and if that's the case, it should be noted in the .ini file(s).


These are tracked for Fission mochitests work at

Summary: Fix failing DOM:Web Authentication tests with Fission → Fix failing DOM:Web Authentication tests with cross-origin

Tracking these test failures for Fission M7 Beta. We need to investigate whether why these tests fail for xorigin && !fission but pass for xorigin && fission. This is probably a test bug.

Fission Milestone: --- → M7

The current list of Web Authentication tests that fail in xorigin mode:,28-31

Some always fail in xorigin mode and some unexpectedly pass when Fission is enabled, which is not good either:

fail-if = (xorigin && !fission)
fail-if = (xorigin && !fission) # NotAllowedError
fail-if = (xorigin && !fission) # NotAllowedError
fail-if = (xorigin && !fission) # NotAllowedError
skip-if = xorigin # Hangs, JavaScript error:, line 76: DataCloneError: The object could not be cloned.
skip-if = xorigin # JavaScript error:, line 76: DataCloneError: The object could not be cloned.
fail-if = (xorigin && !fission) # NotAllowedError
fail-if = (xorigin && !fission) # NotAllowedError
fail-if = (xorigin && !fission) # NotAllowedError
fail-if = xorigin # NotAllowedError

Based on the spec it appears as though some of the APIs being tested require that the calling document have sameOriginWithAncestors be true, while xorigin tests inherently force this to be false, as they're running in a cross-origin iframe, so it's probably expected that these tests will fail under xorigin tests.

it's much more worrying that the tests don't fail with xorigin && fission, as that means that whatever check the webauthn code is doing to make sure that there are no cross-origin ancestors is broken with Fission enabled. I think the root of at least some of this issue is probably the IsSameOriginWithAncestors call, which looks like it's going to be fixed by bug 1579278 - so we should come back to these tests and make sure that they reliably fail in the correct way in xorigin tests after that bug is fixed. Ni? :rmf to take a look at this bug when they're done with bug 1579278.

We should also likely make a test which explicitly makes sure that these tests fail correctly in the xorigin case.

Flags: needinfo?(bugs)
Closed: 4 years ago
Flags: needinfo?(bugs)
Resolution: --- → DUPLICATE
Assignee: nobody → bugs

Martinho, this bug was specifically for fixing these tests that were weirdly failing with xorigin && !fission, which kmag has done in bug 1579278, and now these just fail with xorigin.
You should file a separate bug for fixing these for xorigin, or for marking them as expected failures for xorigin, if they aren't meant to be run in xorigin mode anyway. I see that you've added a new xorigin test to webauthn, that's great but should be done in a separate bug.

Comment on attachment 9203423 [details]
Bug 1685359 - Fix failing DOM:Web Authentication tests with cross-origin

Revision D105315 was moved to bug 1694639. Setting attachment 9203423 [details] to obsolete.

Attachment #9203423 - Attachment is obsolete: true
You need to log in before you can comment on or make changes to this bug.