crbug/601584 and crbug/820617 discover simulated clicks have issue in context of oopif and cross-frame, likely related to this issue. 

This probably just needs a test fix like the one in https://chromium-review.googlesource.com/c/chromium/src/+/1006528/8/third_party/WebKit/LayoutTests/external/wpt_automation/fullscreen/auto-click.js

Though I can't seem to find this test in codesearch?

The CL is still working on progress: https://chromium-review.googlesource.com/c/chromium/src/+/971361

I haven't have time to take a closer look at crbug/820617. But from the fix you gave me it looks like the bug is irrelevant?

My current problem is that neither webtestdriver or gpuBenchmarking API could correctly perform a click on an iframe's element. For webtestdriver, it's just not supported yet: https://cs.chromium.org/chromium/src/third_party/WebKit/LayoutTests/resources/testdriver.js?rcl=7270258e2271da0a2fc622c2e8dd9fa9e059f49c&l=62; for gpuBenchmarking, it's as described here in this bug.

This bug is listed as "stale" according to the CSM triage guidelines. Max, any update on what the timeline is looking like for fixing this?

@nzolghadr, do you know whether we can simulate a click on iframe elements yet?

The NextAction date has arrived: 2018-08-31

Are you using gpu benchmarking or (test_driver) click? There was another bug opened for that as well. Ria was that assigned to you or someone else? I don't seem to be able to find it.

I am currently using gpu-benchmarking. I can switch to test_driver if it support it.

From this line it seems like clicking in iframe is not supported by test driver yet:
https://cs.chromium.org/chromium/src/third_party/WebKit/LayoutTests/resources/testdriver.js?rcl=7270258e2271da0a2fc622c2e8dd9fa9e059f49c&l=62

test_driver underneath goes to gpu benchmarking when running the tests on the try bots. Although it comes after that check. So it is worth giving it a try. But you cannot have that submitted to wpt repo as that is Chrome specific.

the other bug is crbug/877961, but that one is more viz hit-testing specific because it relies on renderers to submit compositor-frame/ hit-test data to receive clicks

+Nicolas, I am looking at https://chromium-review.googlesource.com/c/chromium/src/+/1348855.

According to #14, we shouldn't have moved the tests to wpt as test_driver is chrome specific. But one point I am not clear is why test_driver is in wpt folder if that's the case.
https://cs.chromium.org/chromium/src/third_party/blink/web_tests/external/wpt/resources/testdriver.js

It should be fine to use test_driver in WPT, but not call Chrome's gpu benchmarking directly. I don't know what the plan is there for other browsers but I imagine they should each implement their click versions within the test_driver wrapper.

I see. Thanks for explanation. 

test_driver is that standard API that should work for every vendor. It will call into ChromeDriver and then Chrome Dev tools protocol and something similar for Firefox (call into Gecko driver and whatnot).
However, for the time being it doesn't do that on our try bots and will go through gpu benchmarking directly. But that is just a hack to get the tests running on the try bots. In the meantime, whatever you see on test_driver APIs you can use in wpt tests.

Thanks for explanations. So, we are safe for moving the tests to wpt.

For whether we can perform click on iframe's buttons, I will dig into it at some point.