Dave Pagurek

I think this is only partially resolved, as we don't show the properties of objects anywhere in the reference section of a docs page anymore, they're just hidden. So I...

Those ones you tagged me on are ones I made, yep!

Were you trying to change the capitalization of a file? It looks like it hasn't shown up in got if you check the Files Changes tab of this PR because...

Thanks @akkarn1689! I'll assign this to you, but before going ahead with a full solution, it might make sense to investigate some of the potential paths forward @bojidar-bg mentioned, experimenting...

Is this flaky in some way, e.g. if you run just that one test file with `npm run test test/unit/webgl/p5.RendererGL.js` does it still fail, or is it only when run...

Another thing to test could be parallelism. It looks like by default vitest [runs multiple test files in parallel](https://main.vitest.dev/guide/parallelism.html#file-parallelism), and on some systems WebGL tests might be too heavy to...

@all-contributors please add @LalitNarayanYadav for code

> Maybe we just use the [default iframe](https://github.com/processing/p5.js-website/blob/main/src/layouts/SketchLayout.astro#L81-L87) in that case? One of the reasons why we detect the width/height is so we can change how scaling works on those...

One of the problems with returning an object immediately is that some methods, like loadJSON, don't know what their return value should be immediately. p5 1.x always returns an object,...

Is it a requirement that we overload the existing `load*` functions for this? e.g. if we're ok having both `loadImage` and `lazyLoadImage`, then one could tell users that the `lazyLoad*`...