Closed Bug 1724901 Opened 2 years ago Closed 2 years ago

images/svg in oopif are painted as if resolution of ancestor documents is 1


(Core :: Web Painting, defect)




93 Branch
Fission Milestone MVP
Tracking Status
firefox-esr78 --- disabled
firefox-esr91 --- disabled
firefox91 --- disabled
firefox92 --- disabled
firefox93 --- fixed


(Reporter: tnikkel, Assigned: tnikkel)




(2 files)

If we have something that is rasterized in the child process it knows nothing about any resolution (from pinch zooming or css transforms) in any ancestor document.

This is a webrender only problem. Although we don't plan to use non-wr with fission this works with non-wr because of these two code sites

where send the scale:

where we use that scale:

The equivalent code for webrender is

where we should be sending the scale (sends 1 for scale):

and we never use the scale with webrender.

For most content this is not a problem because webrender rasterizes it in the parent/gpu process after it has assembled the oopif webrender display list into the ancestor documents webrender displaylist so it knows the transform because it's all in one tree at that point. But that doesn't work if the child process is responsible for rasterizing the content (or sending the right sized image).

Fission Milestone: --- → ?

(In reply to Timothy Nikkel (:tnikkel) from comment #0)

where we should be sending the scale (sends 1 for scale):

Bug 1724904 fixes this part.

Depends on: 1724904
See Also: → 1724808

To fix this we'll probably need to get the scale from the BrowserChild like non-wr does, and then incorporate that into the root StackingContextHelper in that process maybe, or something like that.

Assignee: nobody → tnikkel
Fission Milestone: ? → MVP

This ensures images and svg content and anything else rasterized in the content process has the right scale.

Depends on: 1726088
Pushed by
Use the scale from ancestor documents in other processes in the StackingContextHelper. r=jrmuizel
Add test. r=hiro
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 93 Branch

Setting status-firefox92=disabled because Fission is disabled in Fx92 and I don't think we need to uplift this fix just for our Fission experiment planned for Fx92 in the Release channel.

Blocks: 1739015
You need to log in before you can comment on or make changes to this bug.