Closed Bug 1594585 Opened 5 years ago Closed 5 years ago

Fission a11y: Make iframe tests run for both in-process and out-of-process iframes

Categories

(Core :: Disability Access APIs, task, P3)

task

Tracking

()

RESOLVED FIXED
mozilla72
Fission Milestone M5
Tracking Status
firefox72 --- fixed

People

(Reporter: Jamie, Assigned: yzen)

References

Details

Attachments

(2 files)

Right now, Fission isn't enabled by default, but CI runs tests for both Fission disabled and Fission enabled. This means that the tests added in bug 1543575 for iframes will run for both in-process and out-of-process iframes. Once Fission is enabled by default, CI (probably?) won't run the tests with Fission disabled. However, we still want to exercise both in-process and out-of-process iframes, as the code paths are different internally but they should effectively behave the same way from an a11y client's perspective.

We should be able to modify our a11y browser test harness to run the iframe tests twice: once with a same-origin iframe (in-process) and once with a different-origin iframe (out-of-process).

Fission Milestone: --- → Future
Assignee: nobody → yzenevich
Status: NEW → ASSIGNED
Fission Milestone: Future → M5
See Also: → 1597303
Pushed by yura.zenevich@gmail.com:
https://hg.mozilla.org/integration/autoland/rev/5029ec6468df
update wording across accessible b-c tests to differentiate between fission and iframe. r=Jamie
https://hg.mozilla.org/integration/autoland/rev/857a699a8088
add coverage for b-c tests that run in in-process iframes. r=Jamie
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla72
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: