Also:
- Make Dismissable report when it starts squashing, since otherwise we
don't invalidate the list early enough and it gets mad that it wasn't
told one of its children had changed size.
- Have Dismissable check that it gets removed after it's dismissed, to
avoid having lots of redundant widgets around.
- Start tracking the height of each child of a MixedViewport, so that we
don't accumulate floating point errors when a child jiggles up and down.
- Have _childOffsets reuse its storage space rather than newing up a new
copy each time we reset the cache.
- Avoid double-updating child sizes when handling mixed viewport invalidations.
This updates to mojo 4e4d51ce28a and mojo sdk 711a0bcfb141b4 and updates the sky
package's pubspec.yaml dependency to '>=0.1.0 <0.2.0' to be compatible with
the current mojo package. This includes an update to the Mojo Dart generator to
produce real classes for enums and the corresponding updates for users of the
KeyboardType enum in Sky as well as one scoped_ptr->std::unique_ptr in shell
corresponding to a change in the Mojo EDK.
When a new version of the sky and sky_services package are pushed this will fix
domokit/mojo#440.
Remove the Widgets framework's PointerEventListener definition now that
the Rendering layer has one. It was previously clashing in files that
imported both, which would result in it being hidden. Turns out
MineDigger is the only example that this affects.
This change ensures that we only store the results of a hit
test on the initial pointer down event. Moreover, we perform
new hit tests each time a hovering pointer moves. This is
important to ensure correct behavior of input devices which can
hover, such as mice.
Previously the first hover movement after releasing a mouse
button would cause a new pointer state to be recorded along with
hit test results for wherever the pointer happened to be which
caused the following pointer down event to be delivered to the
wrong place.
Fixes issue #1189.
