Fix flakiness in touch-action WPT for deleted element. The test deleted the touch-element on pointerdown, and expected the TestDriver action sequence to keep sending events at a position relative to that element. This assumes, without any supporting documentation, that TestDriver determines the event positions before the first dispatch. My local testing shows otherwise: apparently TestDriver "remembers" the target for latter dispatches in the sequence, which is problematic after the target is deleted on pointerdown. This assumption made the test flaky (and failing on headless). Since this test is about the effect of changes in touch-action and not in DOM, this CL removes this assumption by replacing the DOM change with a touch-action change. Additionally, this CL cleans up the test a bit, and adds attribute to prevent text-selection and drag-and-drop in case these affect the outcome of finger-drag in some platform. Bug: 368980630 Change-Id: Ic0b4c49cd8409f4722cddf2f6b8424c501d6ec0b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6012919 Reviewed-by: Kevin Ellis <kevers@chromium.org> Commit-Queue: Mustaq Ahmed <mustaq@chromium.org> Cr-Commit-Position: refs/heads/main@{#1382965}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.