KhronosGroup / KhronosGroup/WebGL
Consider name validation for getFragDataLocation
Open
- Dominant language
- HTML
- Stars
- 2.9k
- Forks
- 703
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 4
Description
_A follow-up to #3727._
The current WebGL 2.0 specs do not apply the same string validation rules (max length and allowed characters) to the `name` parameter of the `getFragDataLocation` command as to the `name` parameter of `getAttribLocation` or `getUniformLocation`. This is likely an oversight.
Contributor guide
Research direction
No repository files or tests are named in the issue. Start by reading the WebGL 2.0 rules for getFragDataLocation alongside getAttribLocation and getUniformLocation, and review follow-up issue #3727; completion criteria are not specified beyond deciding whether matching name validation should apply.
Written by the indexing model from the issue text.
Assessment
- Domain
- web-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100