Clarify RGB16F_EXT format details and framebuffer support #40382
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
Content:WebAPI
|
Preview URLs |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Fixed incorrect documentation for the EXT_color_buffer_half_float extension regarding
RGB16Fformat support and clarified WebGL version differences.Motivation
The original documentation incorrectly stated that
RGB16F_EXTis always color-renderable, when in fact it has different behavior in WebGL 1.0 vs WebGL 2.0 contexts. This was misleading developers who need to understand the proper usage of this extension across different WebGL versions.Additional details
Reference: WebGL EXT_color_buffer_half_float Extension Specification
Related issues and pull requests
Fixes #39136