[p5.js 2.0 Bug Report]: unexpected behavior from bezier method of graphics object

[Ufuueueuru]

Most appropriate sub-area of p5.js?

• [ ] Accessibility
• [ ] Color
• [x] Core/Environment/Rendering
• [ ] Data
• [ ] DOM
• [ ] Events
• [ ] Image
• [ ] IO
• [ ] Math
• [ ] Typography
• [ ] Utilities
• [ ] WebGL
• [ ] Build process
• [ ] Unit testing
• [ ] Internationalization
• [ ] Friendly errors
• [ ] Other (specify if possible)

p5.js version

v2.0.1

Web browser and version

Firefox 138.0.1

Operating system

Windows 11

Steps to reproduce this

Steps:

1. Use createGraphics to initialize a p5 graphics buffer
2. Run the bezier method within said graphics buffer

It appears that the bezier method within a graphics buffer has the exact behavior as using the global bezier method, drawing to the canvas instead of the graphics buffer. This behavior did not occur in v1.11.5

Snippet:

let g;

function setup() {
  createCanvas(400, 400);
  
  g = createGraphics(200, 200);
}

function draw() {
  g.background(0);
  g.stroke(255, 0, 0);
  g.strokeWeight(5);
  g.noFill();
  g.bezier(0, 0, 100, 0, 0, 100, 200, 200);
  
  
  //Comment out this line and for some reason the bezier gets drawn (to the canvas instead of the graphics object)
  //image(g, 0, 0, 400, 400);
}

Here is the example in the online editor: https://editor.p5js.org/Ufuueueuru/sketches/IV_tAs3qU Notice how in the example the bezier is drawn without any of the stroke color, fill color, and weight changes in v2.0.1, but drawn correctly with those attributes in v1.11.5

[welcome[bot]]

Welcome! 👋 Thanks for opening your first issue here! And to ensure the community is able to respond to your issue, please make sure to fill out the inputs in the issue forms. Thank you!

[perminder-17]

Already fixed via #7829