[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Public WebGL] Uses of WEBGL_debug_renderer_info

We build a HTML5 game engine and have used the unmasked renderer for:
- identifying GPUs affected by driver bugs, and working around it (e.g. "Mali" on Android)
- analytics on the unmasked renderer to identify the impact of such bugs and help us decide how to respond
- identifying which GPU is really in use on dual-GPU systems
- displaying it to the user as a diagnostic (also for them to identify which GPU is in use)

On Thu, 2 May 2019 at 22:42, Ken Russell (kbr@google.com) <public_webgl@khronos.org> wrote:
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?