Khronos Public Bugzilla
Bug 437 - ReadBuffer should be NONE when no default framebuffer exists?
Summary: ReadBuffer should be NONE when no default framebuffer exists?
Alias: None
Product: OpenGL
Classification: Unclassified
Component: API Specification (show other bugs)
Version: 4.1
Hardware: PC All
: P3 normal
Target Milestone: ---
Assignee: Jon Leech
QA Contact:
Depends on:
Reported: 2011-02-13 18:43 PST by Dan Bartlett
Modified: 2013-06-18 15:59 PDT (History)
0 users

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Dan Bartlett 2011-02-13 18:43:14 PST
Currently the OpenGL 4.1 spec (v20100725) reads:

"For the default framebuffer, the initial setting
for ReadBuffer is FRONT if there is no back buffer and BACK otherwise."

This means that if there is no default framebuffer associated with the context, then it will be a value of FRONT, whereas for draw buffers the specification reads:

"For the default framebuffer, in the initial
state the draw buffer for fragment color zero is BACK if there is a back buffer;
FRONT if there is no back buffer; and NONE if no default framebuffer is associated with the context."

Maybe the ReadBuffer should be NONE too when there is no associated framebuffer?
Comment 1 Jon Leech 2013-06-18 15:59:17 PDT
This was fixed in the GL 4.2 spec but we forgot to close the bug. Thanks.