WebGL texImage2D srcData: Clarify null is allowed
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 84/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- javascript, web-dev
- Domain
- documentation
Research direction
The issue points to files/en-us/web/api/webglrenderingcontext/teximage2d/index.md, around line 153. Read the srcData description and nearby format guidance, then clarify whether null is generally allowed and what it means for texture contents. Done when the page states this clearly without implying the allowance applies only to one format.
Written by the indexing model from the issue text.
Description
The line here implies, to me, that the srcData may be null perhaps only if this particular format is used:
Whereas I was looking at the MDN docs to verify whether I can use null for srcData in general (which does seem to be allowed), I didn't catch anywhere this is explicitly stated on this page. A few lines above (before the chart) might be good place to specify this more generally.
Current:
A
TypedArrayorDataViewcontaining the compressed texture data. Its type must match the type parameter:
Possible:
A
TypedArrayorDataViewcontaining the compressed texture data, ornullto allocate storage in the texture without specifying its content (instead, the content will be <undefined/junk? || zeroed?>). Its type must match the type parameter:
- Dominant language
- Markdown
- Stars
- 11.1k
- Forks
- 23.3k
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 165
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from mdn/content
-
Content:CSS needs triage
Difficulty 1/5 Under an hour Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Intl spec updatesOpenContent:JS goal: up-to-date needs BCD update
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
CSS Custom Highlight API: mention StaticRange for highlights that outlive DOM changesPossibly taken @abdul-karim-mia claimed this 1 day ago. OpenContent:WebAPI help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
ARIA page template doesn't document attribute page sectionsPossibly taken A pull request linked to this issue is open or already merged. OpenContent:Meta needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Add new `runtime.MessageSender` `windowId propertyPossibly taken @xeenon claimed this 3 days ago. OpenContent:WebExt needs triage
Difficulty 1/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
BehiSecc/awesome-claude-skills#1354 ·
Maintainers usually reply within 7 days
-
customer report feature-request-triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Codeinwp/optimole-wp#1239 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
agents nolte-linux security skills
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
nolte/claude-shared#732 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 Half a day Newbie friendliness 62/100
modelscope/ms-cookbook#35 ·
Maintainers usually reply within 1 day