Bug: Events are firing twice when we have dynamic and static mode

[danielbarion]

Current Behavior

When we have eventMode = 'static' and eventMode = 'dynamic' in the same app, the events fire twice.

Expected Behavior

When we have eventMode = 'static' and eventMode = 'dynamic' in the same app, the events should fire only once.

Steps to Reproduce

1. Go to https://pixijs.com/8.x/playground?exampleId=events.logger
2. On the following code:

    // Enable interactivity everywhere!
    app.stage.eventMode = 'static';
    app.stage.hitArea = app.screen;
    whiteBox.eventMode = 'static';
    blackBox.eventMode = 'static';

3. Change any of the event modes to be dynamic:

    // Enable interactivity everywhere!
    app.stage.eventMode = 'static';
    app.stage.hitArea = app.screen;
    whiteBox.eventMode = 'dynamic';
    blackBox.eventMode = 'static';

Wait it gets reflected into the playground, the events are now firing twice.

The playground already edited

Another simple example: https://www.pixiplayground.com/#/edit/exDzbrsXsLvgdbWm0iZFG

Environment

• pixi.js version: 8.1.0
• Browser & Version: Version 123.0.6312.87 (Official Build) (arm64)
• OS & Version: Mac OS Ventura 13.2.1 (22D68)
• Running Example: https://www.pixiplayground.com/#/edit/exDzbrsXsLvgdbWm0iZFG

Possible Solution

No response

Additional Information

No response

[CatchABus]

The root cause seems to be here: https://github.com/pixijs/pixijs/blob/dev/src/events/EventTicker.ts#L110
That dispatch might need better handling.

[Nantris]

Great find @CatchABus.

@danielbarion is this not a duplicate of #10131. If it is, I'd encourage you to close this one and join us in discussion over there, but I understand it may be a distinct (albeit related) issue.

[danielbarion]

@Nantris I saw on the issue you mentioned the following: The issue occurs about 90% of the time..

Here the issue happens 100% of the time when we have static event mode and dynamic in the same scenario/app.

I had the issue and a friend from Pixi.js team identified the issue, he asked me to create this issue so the team can work on it when they have time.

So I believe it's better to keep this one open and let the team close it, thanks for sharing the other issue