Closed Bug 1313260 Opened 8 years ago Closed 8 years ago

Fix reftest harness reading nsIGfxInfo from the wrong process

Categories

(Core :: Layout, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla52
Tracking Status
firefox52 --- fixed

People

(Reporter: dvander, Assigned: dvander)

References

Details

Attachments

(1 file)

When the GPU process is enabled, we don't use Direct2D in the UI process. Since the reftest harness reads rasterization settings from the UI, conditions like "fails-if(d2d)" don't work anymore.

Easiest thing to do is have reftest-content.js send up nsIGfxInfo results to the test harness, and have it use those instead.
Attached patch fixSplinter Review
Attachment #8804954 - Flags: review?(matt.woodrow)
Attachment #8804954 - Flags: review?(matt.woodrow) → review+
Pushed by danderson@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/230f4a048880
Parse reftest conditions based on content gfx settings instead of chrome. (bug 1313260, r=mattwoodrow)
https://hg.mozilla.org/mozilla-central/rev/230f4a048880
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla52
You need to log in before you can comment on or make changes to this bug.