Bug 93625 - [WebGL] GraphicsContext3D::deleteFramebuffer is not updating the m_bounds to default framebuffer
Summary: [WebGL] GraphicsContext3D::deleteFramebuffer is not updating the m_bounds to ...
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: Canvas (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL: http://www.opengl.org/sdk/docs/man3/x...
Keywords:
Depends on:
Blocks:
 
Reported: 2012-08-09 10:11 PDT by Alexandru Chiculita
Modified: 2012-08-09 14:16 PDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Alexandru Chiculita 2012-08-09 10:11:00 PDT 
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.
Comment 1 Alexandru Chiculita 2012-08-09 14:16:15 PDT 
WebGL Rendering Context code already has this covered.