Change FilterPoints() to not remove points later than metadata_
Currently, if no point in |points_| has the same timestamp as |metadata_|, everything in the map is erased. However, this sometimes results in some points that have timestamps later than the metadata's being erased. Particularly, this can occur when the API is first used, since the point used to make the metadata wasn't sent to viz by the browser process, since it didn't know to send them yet. However, if it then sends points before this metadata makes it to viz, those points would be erased since none match metadata's timestamp. This could cause future trails to not be drawn too. This change fixes that by only removing points that have timestamps earlier than metadata's timestamp. Bug: 1132043 Change-Id: I1da7b4ca7de8e816cebb67dece7a2bb1743cddf7 Cq-Do-Not-Cancel-Tryjobs: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2429963 Commit-Queue: Mario Bianucci <mabian@microsoft.com> Reviewed-by:weiliangc <weiliangc@chromium.org> Reviewed-by:
Daniel Libby <dlibby@microsoft.com> Cr-Commit-Position: refs/heads/master@{#818179}
Showing
Please register or sign in to comment