When https://github.com/dart-lang/language/issues/1274 (Infer
non-nullability from local boolean variables) is implemented, flow
analysis will detect that code like this no longer needs to perform a
null check:
final bool hasIdentityTransform =
transform == null || isIdentityFloat32ListTransform(transform);
...
if (!hasIdentityTransform) {
... transform! ... // Null check unnecessary
}
To avoid a build failure due to the unnecessary null check, we need to
temporarily write it in a way that we can ignore it. Once the feature
is complete and rolled into flutter, I'll remove the null check
entirely.
This corrects the button state emitted on synthetic pointer move and
hover events generated by the engine.
When an embedder notifies the engine of a pointer up or down event, and
the pointer's position has changed since the last move or hover event,
`PointerDataPacketConverter` generates a synthetic move or hover to
notify the framework of the change in position. In these cases, the
current event from the embedder contains the new button state *after*
the pointer up/down event, but the move/hover needs to be synthesized
such that it occurs *before* the pointer up/down, with the previous
button state.
This patch stores the button state after each pointer down, up, move, or
hover event such that it can be used by the next event if a synthetic
event must be issued.
The bug in the previous logic was revealed by the release of macOS 11
(Big Sur), which appears to issue move events between mouse down and
mouse up, which did not use to be the case.
This fixes https://github.com/flutter/flutter/issues/64961, which is the
desktop-specific tracking bug for the more general Big Sur mouse click
umbrella issue https://github.com/flutter/flutter/issues/71190.
* Revert "Revert "Set SkPath::setIsVolatile based on whether the path survives at least two frames (#22620)" (#23044)"
This reverts commit 4f914253bd7cd2a5cca3fd97213df37494e9bf37.
* Fix tracing
* fixes voice over for higher ios-safari versions
* change enable conditions for webkit
* adding click event for removal. adding unit tests
* run the mobile semantics enabler test on mobile browsers
* remove test method that gave different result on LUCI.(further inv. needed)
* For Firefox focusing on the DOM element after blur propagates
* modify the unit tests. remove webkit skip
* change async testing to a more common usage
