mirror of
https://github.com/penpot/penpot.git
synced 2026-11-16 15:11:17 +00:00
* ✨ Send telemetry for WebGL renderer failures WebGL renderer failures left no trace in the audit log, so we could not tell why people switch WebGL off. - Send webgl-unavailable when the "WebGL is not available" modal shows, with the init error. - Send webgl-context-lost, webgl-context-restored and webgl-reload-failed from the WASM renderer. - Add the active renderer (wasm or svg) to handled-exception, unhandled-exception, exception-page and open-workspace-file. - Add environment details to the WebGL events and to enable/disable-webgl-rendering: normalized GPU family and backend, max texture size, device memory, CPU cores and whether the app runs inside Electron. The full GPU renderer string is not sent, as it can help fingerprint a device. Closes #12984 AI-assisted-by: claude-opus-5-5 * ⚡ Avoid throwaway WebGL contexts in renderer telemetry WebGL events no longer create a context to read GPU details; the settings, menu and unavailable modal create one at most once. AI-assisted-by: claude-opus-5-5 * 🐛 Refresh remembered GPU details on each renderer init A restored context can run on another GPU, so read it on every init instead of only the first one. AI-assisted-by: claude-opus-5-5 * ⚡ Never create a WebGL context for renderer telemetry WebGL events send GPU details only when the renderer has already read them on init, instead of probing a throwaway context. AI-assisted-by: claude-opus-5-5 --------- Co-authored-by: Elena Torro <elenatorro@gmail.com>