Explanation of what is happening here procedurally: * This was originally filed to track a data race in `CancelGesture` * The fix was backed out due to another data race in `UpdateWithTouchAtDevicePoint` * The backout did not fix the `UpdateWithToucAtDevicePoint` data race. It's unclear what caused it to start happening, but in any case, it's a pre-existing issue that was exposed by a recent code change. * The updated patch here fixes both data races * But until that's reviewed, we're landing a temporary suppression
Bug 1642884 Comment 11 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Explanation of what is happening here procedurally: * This was originally filed to track a data race in `CancelGesture` * The fix was backed out due to another data race in `UpdateWithTouchAtDevicePoint` * The backout did not fix the `UpdateWithTouchAtDevicePoint` data race. It's unclear what caused it to start happening, but in any case, it's a pre-existing issue that was exposed by a recent code change. * The updated patch here fixes both data races * But until that's reviewed, we're landing a temporary suppression