emscripten-core/emscripten

missing informative way of extracting WebGL context creation failures

Open

#12,355 opened on Sep 28, 2020

View on GitHub
 (3 comments) (1 reaction) (0 assignees)C++ (3,519 forks)batch import
help wantedwontfix

Repository metrics

Stars
 (27,361 stars)
PR merge metrics
 (Avg merge 19d 10h) (147 merged PRs in 30d)

Description

as discussed here, today the only information that emscripten returns about WebGL context creation failures appears in logs, if the GL_DEBUG or ASSERTIONS flags are set during the build process. There's no programatic way of receiving the source of failure in GL.createContext or emscripten_webgl_create_context, which means that these failures can't be handled in real time, and any logs must be extracted from the console - both of which are problematic when shipping code for production. Something like the proposed emscripten_webgl_create_context_ex should be created, preferably with the ability to extract error information from also from the internal call to GL.createContext.

Contributor guide

Research direction
Study the existing implementation of GL.createContext and emscripten webgl create context to identify where failures happen and how to propagate error messages. Check the discussion in PR #11441 for proposed solutions.
Tech stack
ccpp
Domain
api
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C++Emscripten
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45