Revert "Use async targeting to find drag and drop targets"
This reverts commit 400c3bba. Reason for revert: Findit (https://goo.gl/kROfz5) identified CL at revision 665601 as the culprit for flakes in the build cycles as shown on: https://analysis.chromium.org/p/chromium/flake-portal/analysis/culprit?key=ag9zfmZpbmRpdC1mb3ItbWVyQwsSDEZsYWtlQ3VscHJpdCIxY2hyb21pdW0vNDAwYzNiYmE5YmEwMTRiYmJmODk5YzA3YzVjOTllNjJkZTliYWVjYgw Sample Failed Build: https://ci.chromium.org/buildbot/chromium.win/Win7%20Tests%20%281%29/92132 Sample Failed Step: content_browsertests Sample Flaky Test: WebContentsViewAuraTest.DragDropOnOopif Original change's description: > Use async targeting to find drag and drop targets > > Add callback supports to the RenderWidgetTargeter > and use the async targetting in drag and drop code > and register a callback to send drag events using > the callback. Note that since drag and drop events > aren't WebInputEvent it is not possible to use > FindTargetAndDispatch function of RenderWidgetTargeter > at this time. > > The original CL > https://chromium-review.googlesource.com/c/chromium/src/+/1596840 > was reverted due the added test being flaky. This CL is the same > as the original CL expect it has the same test with another > way of checking the logic. > > TBR=sadrul@chromium.org > > Bug: 804633 > Change-Id: I46f15a2b694c3ad9d3574473c2a46ba13dcbfb79 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1641383 > Reviewed-by: Navid Zolghadr <nzolghadr@chromium.org> > Commit-Queue: Navid Zolghadr <nzolghadr@chromium.org> > Cr-Commit-Position: refs/heads/master@{#665601} Change-Id: Ib44e431fa894a33ce908c2f7defb2ae80d399e8d No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 804633 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1641515 Cr-Commit-Position: refs/heads/master@{#665633}
Showing
This diff is collapsed.
Please register or sign in to comment