Closed Bug 783674 Opened 12 years ago Closed 11 years ago

Potential WebGLContext::Render issues

Categories

(Core :: Graphics: CanvasWebGL, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla26

People

(Reporter: jgilbert, Assigned: jgilbert)

References

Details

Attachments

(1 file, 1 obsolete file)

It looks like not only does WebGLContext::Render not bind to the screen before ReadPixels, but it also doesn't Flush the gfxImageSurface (probably fine), and doesn't MarkDirty the surface. (probably not fine)
Assignee: nobody → jgilbert
Status: NEW → ASSIGNED
Attached patch patch (obsolete) — Splinter Review
Switch to ReadScreen* and mark surfaces as dirty.
Attachment #652894 - Flags: review?(bjacob)
Summary: WebGLContext::Render issues → Potential WebGLContext::Render issues
We can probably make a POC for the framebuffer-dependent part of this bug: Clear the WebGL screen to green, create and bind a framebuffer, and clear the framebuffer to red. Check that Render is showing the green one any number of ways. (toDataURL, upload canvas to a texture, draw canvas to a canvas) This should be added to the conformance suite if it's not already there.
OS: Windows 7 → All
Hardware: x86_64 → All
Attachment #652894 - Flags: review?(bjacob) → review+
Attached patch patchSplinter Review
Unbitrotted, and we only should need to do the MarkDirty part now. The switch to ReadPixelsFromScreen happened elsewhere, and has tests.
Attachment #652894 - Attachment is obsolete: true
Attachment #794889 - Flags: review+
Keywords: checkin-needed
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla26
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: