Is this bug still active? How big of a task would this be? I'm willing to contribute to this one.

Cheers,

From what I can tell it is.

Good resources about it are in ANGLE's src/libANGLE/renderer/gl/renderergl_utils.cpp and src/libANGLE/renderer/gl/formatutilsgl.cpp

Hi,

I checked ANGLE's rendergl_utils.cpp and formatutilsgl.cpp. As far as I can
understand, a table of mappings between internal GL formats,
renderable/texturable/filterable flags and required extensions for each
format needs to be created, and then this table needs to be iterated
against every extension the running hardware supports, right?

If that's the case, then for the purposes of IsES3Capable, do we need to
consider only the ones suported by GLES3? e.g, the ones which require the
extension GL_OES_* and/or the ones under "OpenGL ES texture support" in
formatutilsgl.cpp ?

I'm new to internal WebGL development, so please correct me if I'm wrong
anywhere.

Thanks!


On Fri, Jan 13, 2017 at 6:02 AM, cwal… via monorail <monorail+v2.490334486@
chromium.org> wrote:

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot