KhronosGroup / KhronosGroup/WebGL
Issues with WEBGL_debug extension spec
- Dominant language
- HTML
- Stars
- 2.9k
- Forks
- 703
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 4
Description
A couple of issues with this extension specification came up during a recent face-to-face meeting:
- The MAX_DEBUG_MESSAGE_LENGTH_KHR and MAX_DEBUG_GROUP_STACK_DEPTH_KHR enums should be removed since they're unnecessary (the extension just returns strings to JavaScript).
- The extension should mention that DEBUG_OUTPUT_SYNCHRONOUS was removed. This eliminates undefined behavior from reentrant debug callbacks.
Also, hopefully there won't be issues with needing programs' line numbers to be the first thing on the line, etc. (as with getProgramInfoLog in the past).
Contributor guide
Research direction
Start by locating the WEBGL_debug extension specification and review the definitions of MAX_DEBUG_MESSAGE_LENGTH_KHR, MAX_DEBUG_GROUP_STACK_DEPTH_KHR, and DEBUG_OUTPUT_SYNCHRONOUS. Remove the unnecessary enums, document that DEBUG_OUTPUT_SYNCHRONOUS was removed, and verify the specification addresses the concern about program line-number formatting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100