Open Bug 1682554 Opened 5 years ago Updated 4 years ago

Ensure events don't arrive in CocoaGamepad after StopMonitoring() has been called

Categories

(Core :: DOM: Device Interfaces, defect, P3)

Product:
Core
Component:
DOM: Device Interfaces
Type:
defect

Tracking

()

Status:
ASSIGNED

People

(Reporter: cmartin, Assigned: cmartin)

References

Details

Currently, the Mac OS X implementation of gamepad monitoring in dom/gamepad/cocoa/CocoaGamepad.cpp doesn't have any synchronization code in its StopMonitoring() function. GamepadPlatformService expects all concurrent activity to stop when that call returns, as-is the case with Linux and Windows. This triggered an assertion meant to catch this incorrect behavior, causing Bug 1681682.

Severity: -- → S3
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.