Thanks for taking this on @Forchapeatl! We're also a few weeks away from releasing p5 2.0, which lives on the dev-2.0 branch, and has a beta you can try out here: https://github.com/processing/p5.js/releases/tag/v2.0.0-beta.3

I think this is still worth merging into the main branch, but we should also test if the same issue is needed in 2.0, and if we need to make a second PR into dev-2.0 with a similar fix?

Thank you @davepagurek , it the issue replicates in the beta 2.0 . Should I create a PR for the dev-2.0 branch ?

That would be great, thanks!

Please this is the new PR for dev2.0 branch. I have to close this one

@Forchapeatl we can re-open this PR and merge it into main as well, since we will likely release another p5 1.x release with bug fixes in the future. Is everything else in this one good to go?

Yes it works as expected now. It can be tested here https://editor.p5js.org/forchapearl1/sketches/96C3TOR8y

Thanks @Forchapeatl!