WEBGL_debug_shaders getShaderTranslatedSource() should succeed if shader translation succeeded

NEW
Unassigned

Status

()

Core
Canvas: WebGL
P3
enhancement
a year ago
10 months ago

People

(Reporter: Jukka Jylänki, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [gfx-noted])

(Reporter)

Description

a year ago
Currently it looks like calling the function getShaderTranslatedSource() from WEBGL_debug_shaders extension will succeed only if shader compilation succeeded. However this limits some of the purpose of the extension, which is to be able to debug what the translated shader was if it fails to compile.

getShaderTranslatedSource() should succeed if shader translation succeeded, independent of whether compiling the translated shader succeeds or fails. That way it will be possible to call getShaderTranslatedSource() to diagnose bugs in the shader translation process itself.

See bug 1364930 as a test case: the shader fails to compile due to a bug in shader translation, and calling getShaderTranslatedSource() gives

> Error: WebGL warning: getShaderTranslatedSource: Shader has not been successfully compiled.

Translation itself had succeeded to be able to attempt to compile, so it would be good to be able to see the translated shader here.
(Reporter)

Updated

a year ago
Severity: normal → enhancement
Whiteboard: [gfx-noted]
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.