New issue
Advanced search Search tips

Issue 923497 link

Starred by 2 users

Issue metadata

Status: Started
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 3
Type: Bug



Sign in to add a comment

gpuBenchmarking synthetic gestures don't work in OOPIFs

Project Member Reported by mcnee@chromium.org, Jan 18 (4 days ago)

Issue description

Chrome Version: 73.0.3675.0

What steps will reproduce the problem?
(1) Run chrome with --enable-gpu-benchmarking
(2) Visit csreis.github.io/tests/cross-site-iframe-simple.html
(3) Run the following in the iframe's javascript context

var x = 300; var y = 300;
var pointerActions =
            [{source: "touch",
              actions: [
                { name: "pointerDown", x: x, y: y },
                { name: "pointerMove", x: x, y: y - 20 },
                { name: "pointerMove", x: x, y: y - 40 },
                { name: "pointerMove", x: x, y: y - 60 },
                { name: "pointerMove", x: x, y: y - 100 },
                { name: "pointerUp" }]}];
chrome.gpuBenchmarking.pointerActionSequence(pointerActions);

What is the expected result?
The frame should scroll, as it would if --disable-site-isolation-trials were used.

What happens instead?
The frame does not scroll and we reach SyntheticGestureTargetBase::DispatchWebTouchEventToPlatform.


Furthermore, some gestures have a check in the renderer whether the coordinates are within the view, and the child renderer thinks the view is 0x0. So,

chrome.gpuBenchmarking.pinchBy(2.0, 100, 100, undefined, undefined, chrome.gpuBenchmarking.MOUSE_INPUT)

produces the error "Anchor point not in bounds"
 

Comment 1 by mcnee@chromium.org, Jan 18 (4 days ago)

Cc: bokan@chromium.org
Owner: mcnee@chromium.org
Status: Started (was: Untriaged)
I have a fix for the browser side of things which will cover pointerActionSequence, but not the renderer side checks.

Sign in to add a comment