[p5.js 2.0 Beta Bug Report]: Permission denied to access property "pointerType"

[davepagurek]

Most appropriate sub-area of p5.js?

• Accessibility
• Color
• 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

2.0 beta 1

Web browser and version

Firefox 134.0.2

Operating system

MacOS 15

Steps to reproduce this

I've noticed on some sketches, I get this error when trying to run them:

Uncaught Error: Permission denied to access property "pointerType"

Here is a recent example: https://openprocessing.org/sketch/2529270

I think this happens when I'm moving the mouse as the sketch loads? e.g.:

Screen.Recording.2025-02-01.at.4.48.50.PM.mov

[davepagurek]

Update: this doesn't seem to happen on Chrome when I load the same sketch there.

I notice this doesn't happen on Firefox on the p5 web editor, so maybe this is related to OpenProcessing? https://editor.p5js.org/davepagurek/sketches/TUGdYU177

On Safari I get this on OP, but nothing in the p5 web editor:

Maybe something about the new p5 pointer event implementation isn't meshing well with OP's iframe sandboxing? cc @msawired in case you have any ideas!

[msawired]

I couldn't repeat the issue on my computer. Is it causing any issues with the sketch? Such as freezing as such?
"+esm" files are the ones loaded from jsdelivr, so could be some libraries.

[davepagurek]

Thanks for testing it out! It doesn't seem to affect how the sketch runs, or at least it's not a recurring error so maybe it just happens when trying to access the initial mouse position but then stops being a problem? The only adverse side effect is this big error popping up when the sketch runs:

As for libraries, this is only including these:

<script src="https://openprocessing.org/openprocessing_sketch.js"></script>
<script src="https://davepagurek.com/stuff/p5/p5-2.0-b1.min.js"></script>

...so it seems likely to be something specific to the 2.0 beta build.

[msawired]

I checked again but I can't repeat the issue. Maybe relates to some browser setting or an extension? The native console error you see is coming from Sentry, which expected, and this should not show up in the editor console.

[davepagurek]

It still happens in a private window with no extensions for me, but it might be a specific browser or platform version thing. I'll close this since it seems to be fairly limited in scope, and doesn't actually affect how the sketch runs. We can keep an eye on this to see if it ends up being more widespread.