chromium/safari not respecting cross origin image/video
Open
Nobody has claimed this yet.
needs dependencies fixed
video
- Dominant language
- JavaScript
- Stars
- 17.6k
- Forks
- 4.4k
- PR merge metrics
- No merged PRs in 30d
Description
it is showing in chrome but not webvr chromium
WebGL: INVALID_VALUE: texImage2D: no video
255aframe.io/:1 [.WebGLRenderingContext-0x7fa76bfa72a0]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
Contributor guide
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 reproducing the reported cross-origin image/video case in Chrome, WebVR Chromium, and Safari, then inspect the WebGL texImage2D error and render warnings. Done means the affected browsers respect cross-origin media textures without the reported errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100