Remove surface range check when building hit test data
HitTestDataBuilder is checking that the start() and end() of a surface range have the same FrameSinkId before including the surface quad in hit test data. This can prevent OOP-IFs from being clicked during the first four seconds after a page navigation. Instead, remove this check. If there is no surface available for the end FrameSinkId, then an async hit test will be used to target input events. Bug: 926194 Change-Id: I574bf104cd3524973152035e59701a0105908fa9 Reviewed-on: https://chromium-review.googlesource.com/c/1465078Reviewed-by:Ken Buchanan <kenrb@chromium.org> Reviewed-by:
Ria Jiang <riajiang@chromium.org> Commit-Queue: Sean Gilhuly <sgilhuly@chromium.org> Cr-Commit-Position: refs/heads/master@{#635738}
Showing
Please register or sign in to comment