At Onshape we use WEBGL_debug_renderer_info for a few purposes:1. To work around driver-specific interactions with our system. More often than not this involves disabling a feature of our renderer that is exhibiting poor performance on a particular platform/GPU combination. If possible, we will try to find an alternative solution that performs well on all platforms, but this is not always feasible.
Dear WebGL community,There have been some recent discussions about the exposure of the WEBGL_debug_renderer_info extension, as it relates to user privacy and fingerprinting.If you build a WebGL application that queries this extension, could you please reply (either on-list, or directly to me) and indicate what information you infer, directly or indirectly, from it? Could the WebGL API provide this information via a different mechanism?Thanks,-Ken