tree 04d1eec1073ae878c0199b256cf16a11c888a3a9
parent e69a06665de2c98531d6173dab86b8a48d20056e
author Hiroki Kumazaki <kumagi@google.com> 1647594287 +0000
committer Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> 1647594287 +0000

No stride is required for BadTapTarget detection

Timer check stride is actually not required rather waste of resource.
Checking timer every 32 loop sometimes cause timebudget exceeds and saves little resource.
In my local benchmark, every Time::Now() consumes about 20ns and single element check loop consumes about 20us.
32 elements check stride sometimes gets glitch and consumes more than 5ms.
Then we should not have stride during DOM traversal.

Change-Id: I3743151af118b0d07ff6359c9b8257fe78f2d5e5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3513526
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Commit-Queue: Hiroki Kumazaki <kumagi@google.com>
Cr-Commit-Position: refs/heads/main@{#982636}