Chrome bug w/ attrib locations
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 122
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
attribute locations for shaders seem buggy in chrome.
Try running test.js in kami-mesh with normals but leave them out of the main function of the vertex shader so they get optimized away by compiler. The scene will run fine in FF but not in chrome.
Also noticed that specifying vertex attributes manually (see ShaderProgram constructor) is buggy in Chrome.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running test.js in kami-mesh with normals omitted from the vertex shader's main function, comparing Chrome with Firefox. Then inspect the ShaderProgram constructor and its manual vertex-attribute handling. Done means the shader and manually specified attributes behave correctly in Chrome as well as Firefox.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- computer-graphics
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100