Closed
Bug 845693
Opened 12 years ago
Closed 5 years ago
Add reftest support for nested content processes
Categories
(Testing :: Reftest, defect)
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.
Updated•10 years ago
|
Blocks: nested-oop
![]() |
||
Updated•6 years ago
|
Blocks: oop-frames
Updated•6 years ago
|
Comment 1•5 years ago
|
||
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.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•