Most appropriate sub-area of p5.js?
p5.js version
main branch (verified on https://github.com/processing/p5.js as of April 25, 2026)
Web browser and version
N/A — documentation/comment typos, not a runtime bug
Operating system
N/A — documentation/comment typos, not a runtime bug
Steps to reproduce this
This is a documentation/comment fix rather than a runtime bug, so the standard reproduction steps don't apply. Both typos were verified to exist on the current main branch.
Typo 1: widhts → widths
File: src/core/helpers.js (line 19)
// For negative widhts or heights, the absolute value is used.
// ^^^^^^
Typo 2: coordiante → coordinate (appears twice)
File: src/webgl/p5.RendererGL.js (lines 323–324)
In the JSDoc for the pixel-read function:
* @param {Number} x The x coordiante to read, premultiplied by pixel density
* @param {Number} y The y coordiante to read, premultiplied by pixel density
Notes
- Both occur in JSDoc/inline comments only; no runtime behavior is affected.
- The
coordiante typo will surface in the generated reference for anyone reading the JSDoc on the website.
- I'd like to fix this myself if approved.
Most appropriate sub-area of p5.js?
p5.js version
main branch (verified on https://github.com/processing/p5.js as of April 25, 2026)
Web browser and version
N/A — documentation/comment typos, not a runtime bug
Operating system
N/A — documentation/comment typos, not a runtime bug
Steps to reproduce this
This is a documentation/comment fix rather than a runtime bug, so the standard reproduction steps don't apply. Both typos were verified to exist on the current
mainbranch.Typo 1:
widhts→widthsFile:
src/core/helpers.js(line 19)Typo 2:
coordiante→coordinate(appears twice)File:
src/webgl/p5.RendererGL.js(lines 323–324)In the JSDoc for the pixel-read function:
Notes
coordiantetypo will surface in the generated reference for anyone reading the JSDoc on the website.