Skip to content

Fix and clarify language around drawingBufferStorage and RGB8/RGBA8.#3759

Open
kdashg wants to merge 1 commit intoKhronosGroup:mainfrom
kdashg:renderable-rgb8-webgl1
Open

Fix and clarify language around drawingBufferStorage and RGB8/RGBA8.#3759
kdashg wants to merge 1 commit intoKhronosGroup:mainfrom
kdashg:renderable-rgb8-webgl1

Conversation

@kdashg
Copy link
Contributor

@kdashg kdashg commented Feb 17, 2026

Two functional changes here:

  1. Allow RGB8 for drawingBufferStorage, because it's a normal value for drawingBufferFormat.
  2. As such, add RGB8 to WebGL1RenderingContext.

But also: Clarify that this doesn't mean you can use it for e.g. texImage2D.

Fixes #3669.

Two functional changes here:
1. Allow RGB8 for drawingBufferStorage, because it's a normal value for drawingBufferFormat.
2. As such, add RGB8 to WebGL1RenderingContext.

But also: Clarify that this doesn't mean you can use it for e.g. texImage2D.

Fixes KhronosGroup#3669.
@kdashg
Copy link
Contributor Author

kdashg commented Feb 17, 2026

@lexaknyazev FYI ^

@kenrussell
Copy link
Member

Thanks Kelsey for this contribution!

WebGL WG 2026-02-19: resolved to incorporate this, but want to update the conformance tests at the same time. We'd prefer to make those changes and push them to this branch before merging. Or, Kelsey, if it's possible for you to make those updates in this PR we'd appreciate it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Clarify RGBA8/RGB8 usage with WebGL 1.0

2 participants

Comments