Closed Bug 1270509 Opened 8 years ago Closed 8 years ago

Enable some tests on e10s which seem to work fine

Categories

(Core :: DOM: Content Processes, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla49
Tracking Status
e10s + ---
firefox49 --- fixed

People

(Reporter: nika, Assigned: nika)

References

(Blocks 1 open bug)

Details

Attachments

(3 files)

These are a few tests which are currently disabled on e10s, which (at least seem) to work fine when run in e10s.
Blocks: e10s-tests
tracking-e10s: --- → +
Attachment #8749194 - Flags: review?(enndeakin) → review+
Comment on attachment 8749195 [details] [diff] [review]
Enable browser_xhr_sandbox.js on e10s

It looks like this test creates a non-remote content iframe in the hidden window then does some sandbox related checking on it. I presume we also want to test this for remote frames. I'm not the right person to review what should be done here. Perhaps one of the test author or reviewers?
Attachment #8749195 - Flags: review?(enndeakin)
Comment on attachment 8749195 [details] [diff] [review]
Enable browser_xhr_sandbox.js on e10s

It looks like bz has reviewed changes to this test before. r?-ing him.
Attachment #8749195 - Flags: review?(bzbarsky)
Comment on attachment 8749195 [details] [diff] [review]
Enable browser_xhr_sandbox.js on e10s

r=me if it's green on try
Attachment #8749195 - Flags: review?(bzbarsky) → review+
Comment on attachment 8749193 [details] [diff] [review]
Enable test_bug482935.html on e10s

Assuming the test passes on e10s, r+. Give it couple of try runs.
Attachment #8749193 - Flags: review?(bugs) → review+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: