ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #p5js
The goal is to understand whether the p5.js preload() function considers an asset load complete when the browser blocks the request due to an invalid SSL/TLS certificate. When a sketch is served over HTTPS and attempts to load an image from an external domain presenting a self‑signed or expired certificate, the browser’s mixed‑content check aborts the networ
Goal Determine whether loadSound() should automatically start playback after a p5.js or p5.sound upgrade, while respecting browser autoplay restrictions. Constraints Modern browsers block audio that starts without a user gesture. loadSound() currently returns a p5.SoundFile that must be explicitly played, and the underlying AudioContext begins in a suspended
p5.js loadImage() ↔ Browser Image Loading When an image is requested with loadImage() , p5.js internally creates an HTMLImageElement and attaches onload and onerror callbacks. The library offers a timeout argument, but this merely stops the callback from firing after a set period; it does not abort the underlying network request or clear the image source. No
Decision Context When building a medium‑size interactive visualization that will share a page with other scripts and may rely on external add‑ons that expect p5 globals, the developer must choose between p5.js’s global mode and instance mode. Global mode offers direct access to functions like createCanvas and loadImage without wrapping, but it places those i
When a p5.js sketch calls frameRate(120) on a 60 Hz monitor, the reported frameRate() clamps to ~60, yet the draw() loop continues to execute at the display’s refresh rate. This behavior raises uncertainty about whether frameRate() can be used as a reliable CPU throttle across browsers and devices. The goal is to determine if setting a target FPS actually li