Fix: Preserve canvas position when calling noSmooth() in WEBGL

[ImRAJAS-SAMSE]

Resolves #7548

Changes:

• Prevent unnecessary canvas recreation: Modified _resetContext() in p5.RendererGL.js to check if antialias is already false, avoiding redundant resets.
• Preserve canvas positioning: Before recreating the canvas, store position, top, and left attributes, then restore them after recreation.
• Update documentation: Clarified in src/core/shape/attributes.js that noSmooth() may recreate the canvas when called in draw().

Before (Bug Occurs)

• Running noSmooth() in draw() caused the canvas to reset to (0,0) instead of staying in its assigned position.

After Fix

• The canvas remains in position even when noSmooth() is called.
• WebGL rendering works as expected, with jagged edges applied.

(Attach is the screenshot of test file running correctly: The sphere should be rendered inside a blue canvas at position (150,50).)

---

✅ PR Checklist

• npm run lint passes
• Inline reference is included / updated
• Unit tests are included / updated

[davepagurek]

Thanks for making a PR! Two things to help make this more reviewable:

• We're currently working on developing p5 2.0, which is in the dev-2.0 branch and not the main branch, and have temporarily frozen merges into main. Could you base your changes off of that branch and make your PR's base branch dev-2.0?
• It looks like an auto formatter got run on the codebase, so the Files Changed tab of the PR has lots of unrelated changes. Could you make your changes without that turned on so it's easier to see what changes relate to the issue at hand?

[ImRAJAS-SAMSE]

Hi @davepagurek, thanks for your patience!

I tried rebasing my branch onto dev-2.0 as requested, but I ran into a lot of conflicts and unintended changes from previous commits that were already in main.

Would it be better if I reset my branch and recreated the PR with only the necessary changes? That way, the PR will be clean and contain only the actual fix for noSmooth() in p5.RendererGL.js and the documentation update.

Let me know the best way to proceed! Thanks.

[davepagurek]

Agreed, I think it's probably easiest to just manually re-apply the changes on top of dev-2.0. We've added a lot of changes between dev-2.0 and main so rebasing is unfortunately pretty difficult.

[ImRAJAS-SAMSE]

I have created a new clean PR based on dev-2.0 as suggested: #7568

[ImRAJAS-SAMSE]

This issues has been resolved #7568