[roll] Roll fuchsia [ui][input] merge consecutive move-only touch events In the touch input pipeline, processing every intermediate movement event within a single batch can create unnecessary overhead. This is especially prevalent when multiple events in a sequence only update contact positions without adding or removing touch points. Update the touch binding logic to identify move-only events and remove redundant intermediate updates. If two consecutive events in a batch are both move-only, the first is discarded. This optimization reduces the volume of events processed by the pipeline while ensuring the final contact state is preserved. Original-Bug: b/475285439 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1489286 Original-Revision: 129d86b84ad6ec54da52f3bc518797ffb7fd202c GitOrigin-RevId: bb5ab4e6bf29433df435d681b4c3fa8fdc332e56 Change-Id: I743a7c81611d75392618adcb174b7bf12bde7697
This repository contains Fuchsia's Global Integration manifest files.
All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.
Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance in one of the communication channels documented at get involved.
First install Jiri.
Next run:
$ jiri init $ jiri import minimal https://fuchsia.googlesource.com/integration $ jiri update
Third party projects should have their own subdirectory in ./third_party.