You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
153.0.8010.53 (Official Build) (64-bit) (cohort: Stable Installs & Version Pins)
Actual Behavior
When creating a point the visuals seems to disappear after an x value of 256 on any canvas size.
Checked strokeWeight, stroke, coding structure.
This seems to only happen on the Windows version, as Chromebook will show show the point.
Expected Behavior
I'm expecting to see points no matter the version of the browser used to create the object.
Steps to reproduce
Steps:
Snippet:
steps:
1.createapointatlocation(255,(anyyvalue))2.increasethexvalueto256.eg(256,300);3.pointdisappearsvisuallyoncanvas// Paste your code here :)functionsetup(){createCanvas(400,400);background(255);strokeWeight(25);point(256,300);}
Hi! I’d like to work on this issue as part of the Build 2026 × ByteAsk Open-Source Challenge.
The x=255 → x=256 boundary looks particularly interesting, especially since the behavior appears to be Windows-specific. I’d like to first reproduce it across Windows/browser configurations, trace where the point rendering starts failing at that boundary, and then add a regression test alongside the fix.
I’ll keep the change focused on the underlying rendering issue rather than changing the expected "point()" behavior.
Would it be okay for me to investigate and submit a PR for this?
When using the version switcher in the p5.js editor, the points show up with version <= 2.3.0, the first time the bug shows up for me is with version 2.3.1.
For me the bug also occurs when using Chrome while Firefox still works.
Activity
aniruddh18122006-cyber commentedon Oct 8, 2026
Hi! I’d like to work on this issue as part of the Build 2026 × ByteAsk Open-Source Challenge.
The x=255 → x=256 boundary looks particularly interesting, especially since the behavior appears to be Windows-specific. I’d like to first reproduce it across Windows/browser configurations, trace where the point rendering starts failing at that boundary, and then add a regression test alongside the fix.
I’ll keep the change focused on the underlying rendering issue rather than changing the expected "point()" behavior.
Would it be okay for me to investigate and submit a PR for this?
Tainmere commentedon Oct 12, 2026
When using the version switcher in the p5.js editor, the points show up with
version <= 2.3.0, the first time the bug shows up for me is with version2.3.1.For me the bug also occurs when using Chrome while Firefox still works.