Controller VS Keyboard behavior not similar

Problem Description

The controller behavior and the keyboard behavior are not behaving the same way to trigger a "on pressed" event.

The controller will trigger the event the following tick where the button has been pressed.

The keyboard will trigger the event at the same tick where the button has been pressed.

Attach a Capx

we.tl/fSh5LLTTM0

Description of Capx

switch the animation of the sprite with keyboard or controller to compare. Launch in debug mode to make it tick by tick.

Steps to Reproduce Bug

step 1

create 1 sprite with 2 animations :

step 2

on gamepad button pressed :

IF sprite animation = A, set to B

ELSE set to A

on keyboard button pressed :

IF sprite animation = A, set to B

ELSE set to A

Observed Result

The event is not triggered during the same tick depending of which behavior is used

Expected Result

Both behaviors keyboard and controllers should trigger during the same tick

Affected Browsers

• Chrome: (YES)
• FireFox: (YES)
• Internet Explorer: (YES)

Operating System and Service Pack

Windows 10

Construct 2 Version ID

227

Actually Ashley and R0J0hound answered this already in this topic :

I wonder if something couldn't be made in the software to give a clue about that difference that can be very important. Maybe a different color for the arrow icon for trigger conditions that are "fake triggers" ?

Closing as won't fix (and closing the other issue too): this basically comes down to the fact the gamepad API in the browser doesn't trigger events in the same way keyboard events do. The browser API should be updated, and hopefully it will soon...