Open Bug 1643236 Opened 4 years ago Updated 3 months ago

Incorrect rendering of perspective transformed pictures that intersect the viewport bounds


(Core :: Graphics: WebRender, defect, P3)





(Reporter: cbrewster, Unassigned)


(Blocks 2 open bugs)



(2 files)

Attached file test-case.html

(Moving from bug 1642549)

We sometimes incorrectly render pictures with perspective transforms that intersect the viewport bounds. When looking at the render targets, it looks like we clip too much of the transformed picture's content. This leads to the texture stretching at its UV bounds seen in the test case.

Attached image screenshot.png
Severity: -- → S2
Flags: needinfo?(jbonisteel)
Blocks: wr-79
No longer blocks: gfx-triage

Hey Jeff - I see you have marked this as blocking wr-79 - what are the next steps? Who should look at this?

Flags: needinfo?(jbonisteel) → needinfo?(jmuizelaar)

Perhaps Dzmitry or Connor? I'm not actually certain of the severity of this so put in wr-79 so we wouldn't forget about it. If it's not severe than we can drop it from the list.

Flags: needinfo?(jmuizelaar)

Hey Kvark, Connor - can either of you comment on the severity of this issue? Is this something we should fix right away?

Flags: needinfo?(dmalyshau)
Flags: needinfo?(connorbrewster)

I don't think this is urgent/blocking, unless there is a popular resource that happens to be affected.
If Connor is right, and shifting the near plane is enough, this is fairly easy to test.

Flags: needinfo?(dmalyshau)
Severity: S2 → S3
Priority: -- → P3

I did some testing with mozregression and it looks like this bug has been around for a while, it is present in builds going back to early 2019 (builds before this did not handle perspective rendering properly at all). Since we haven't had any reports of this being a problem, I think this is low severity.

That being said, it is noticeable when moving really close to the walls and looking around in the CSS FPS demo:

Flags: needinfo?(connorbrewster)
Blocks: wr-correctness
No longer blocks: wr-79
You need to log in before you can comment on or make changes to this bug.