Closed Bug 845693 Opened 9 years ago Closed 2 years ago

Add reftest support for nested content processes

Categories

(Testing :: Reftest, defect)

x86_64
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: cjones, Unassigned)

References

(Blocks 1 open bug)

Details

I /think/ doing this should be almost trivial.  The current setup looks like

 <window>
  <iframe remote>
 ---[process boundary]---
    <remote content>

We should instead be able to just do

 <window>
   <iframe remote src="proxy.html">
 ---[process boundary]---
     <iframe remote>
     ---[process boundary]---
       <remote content>

The proxy page would have no background/margins/borders/style and just contain an unstyled <iframe remote>.

We would then have to add a reftest-content-proxy.js testing script that bounced messages between reftest.js and reftest-content.js.
Blocks: fission
No longer blocks: oop-frames

Reftests should work with fission. We have a special path for taking snapshots that reftests use with e10s called WIDGET_LAYERS [1]. This path gets the snapshot from the compositor which will contain all content from OOP-iframes.

[1] https://searchfox.org/mozilla-central/rev/1133b6716d9a8131c09754f3f29288484896b8b6/layout/painting/nsDisplayList.h#3479

Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.