Bug 93625
| Summary: | [WebGL] GraphicsContext3D::deleteFramebuffer is not updating the m_bounds to default framebuffer | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Alexandru Chiculita <achicu> |
| Component: | Canvas | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED INVALID | ||
| Severity: | Normal | ||
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://www.opengl.org/sdk/docs/man3/xhtml/glDeleteFramebuffers.xml | ||
Alexandru Chiculita
According to the documentation of glDeleteFramebuffer, "if a framebuffer that is currently bound to one or more of the targets GL_DRAW_FRAMEBUFFER or GL_READ_FRAMEBUFFER is deleted, it is as though glBindFramebuffer had been executed with the corresponding target and framebuffer zero".
Currently, the m_boundFBO is not reset to the default value, meaning that the next call to the bindFramebuffer will avoid to set the same framebuffer id. As soon as the old framebuffer is deleted, GL is allowed to reuse the same identifier for the newly created framebuffers.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Alexandru Chiculita
WebGL Rendering Context code already has this covered.