Skip to content

Commit 8745b31

Browse files
adi-rayJosh-Cena
andauthored
Clarify RGB16F_EXT format details and framebuffer support (mdn#40382)
* Clarify RGB16F_EXT format details and framebuffer support * Update index.md --------- Co-authored-by: Joshua Chen <sidachen2003@gmail.com>
1 parent b88824d commit 8745b31

File tree

1 file changed

+9
-4
lines changed
  • files/en-us/web/api/ext_color_buffer_half_float

1 file changed

+9
-4
lines changed

files/en-us/web/api/ext_color_buffer_half_float/index.md

Lines changed: 9 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -22,17 +22,22 @@ WebGL extensions are available using the {{domxref("WebGLRenderingContext.getExt
2222
- `ext.RGBA16F_EXT`
2323
- : RGBA 16-bit floating-point color-renderable format.
2424
- `ext.RGB16F_EXT`
25-
- : RGB 16-bit floating-point color-renderable format.
25+
- : RGB 16-bit floating-point format. In WebGL 1.0, this may be color-renderable (implementation-dependent). In WebGL 2.0, this format is not color-renderable.
2626
- `ext.FRAMEBUFFER_ATTACHMENT_COMPONENT_TYPE_EXT`
27-
- : ?
27+
- : Passed to {{domxref("WebGLRenderingContext.getFramebufferAttachmentParameter()")}} to get the framebuffer type.
2828
- `ext.UNSIGNED_NORMALIZED_EXT`
29-
- : ?
29+
- : The framebuffer contains unsigned fixed-point components.
3030

3131
## Extended methods
3232

3333
This extension extends {{domxref("WebGLRenderingContext.renderbufferStorage()")}}:
3434

35-
- The `internalformat` parameter now accepts `ext.RGBA16F_EXT` and `ext.RGB16F_EXT`.
35+
- In WebGL 1.0 contexts, the `internalFormat` parameter now accepts `ext.RGBA16F_EXT` and `ext.RGB16F_EXT`. However, `ext.RGB16F_EXT` support is optional and applications must check framebuffer completeness to determine if it's supported.
36+
- In WebGL 2.0 contexts, the `internalFormat` parameter now accepts `ext.RGBA16F_EXT`. The `RGB16F` format is not color-renderable in WebGL 2.0.
37+
38+
It extends {{domxref("WebGLRenderingContext.getFramebufferAttachmentParameter()")}}:
39+
40+
- In WebGL 1.0 contexts, the `pname` parameter now accepts `ext.FRAMEBUFFER_ATTACHMENT_COMPONENT_TYPE_EXT`. An `INVALID_OPERATION` error is generated if `attachment` is `DEPTH_STENCIL_ATTACHMENT` and `pname` is `FRAMEBUFFER_ATTACHMENT_COMPONENT_TYPE_EXT`. When `pname` is `ext.FRAMEBUFFER_ATTACHMENT_COMPONENT_TYPE_EXT`, `getFramebufferAttachmentParameter()` returns either `gl.FLOAT` or `gl.UNSIGNED_NORMALIZED_EXT` for floating-point or unsigned fixed-point components respectively.
3641

3742
## Examples
3843

0 commit comments

Comments
 (0)