tsrwebgl@: When you're unable to tap the uninstall button - does both touch and mouse input not work? Are other things on the screen also unclickable or just the uninstall button?

+afakhry@: do you know who should look into this on the CrOS side?

It's not clear to me from the description if it's a browser or ARC++ issue. It says "Google Play Store", does that mean the web version of the Play Store? 

I tried the web version, and it doesn't have an Uninstall button. It just shows "Installed" once the app is installed. Things seem to work fine for me in all orientations.

+oshima@, and +sadrul@ in case this is ARC++ related.

Upon looking in this more, I believe they are separate issues. Issues with ARC seem to be fixed in 70.0.3538.7.

 Looking into the duo 2FA page (duo), I realized the element that is unresponsive on the webpage is an iframe, which would be a blink problem. I can't figure out what causes the bug. I've tried disabling all of my extensions and using incognito mode and neither of them fix the issue. Oddly enough though, sometimes it just works, though more often than not, it doesn't. When opening the iframe in a new tab, the webpage responds properly. This still isn't working in 70.0.3538.7.

afakhry@, By uninstall, I was referring to right clicking on the app in the Chrome OS app drawer and clicking "uninstall." With the redesign of the drawer in 70.0.3538.7, this was resolved.

Can you post detailed repro steps for the issue on the duo page. 

bokan@ hope this helps

Deleted: Sep 6, 2018 3_43 PM.webm 7.2 MB

	Sep 6, 2018 3_43 PM.webm 7.2 MB View Download

It is possible that this is oopif related. Can you confirm if the iframe is in a separate process from the main-page?

Yes, this is definitely an OOPIF.

Update:

After all this time, I've found a workaround! Minimizing the page and reopening often times solves this, though it may not work the first time.

+cc'ing some OOPIF folks

+riajiang@

Could this be related to  issue 860356 ? That was fixed, but it looks similar.

kenrb@ It doesn't have anything to do with it being in tablet mode, so I personally doubt it.

If it's oopif related, we should be able to bisect this. That might be a good starting point (especially if we can get away with not having to update the CrOS test image underneath).

We would need a page with repro steps for the bisect, though.  That's tough on the example in comment 7, since it appears to require login.

Does the problem repro on a simpler page with OOPIFs, like http://csreis.github.io/tests/cross-site-iframe-simple.html?  If not, have you come across one that we could observe the problem without logging in?  (It sounds like the apps described in the original report might have been a different issue.)  Thanks!

Potentially related:  bug 877762 

There we seem to not be routing gestures to the correct process. Scrolling in the PDF doesn't work but on one of the reproducing machines clicking/tapping on an extension popup also wasn't working.

tsrwebgl@: could you paste the entries under "Variations" on chrome://version

bokan@:

Variations	2c707b42-ca7d8d80
411b6d4e-f23d1dea
b7d3b6c2-f23d1dea
fe69e053-94941f92
9d7f502c-d5d68bac
d01ab0d3-f23d1dea
3e006338-3f4a17df
1a0d11d4-2f9febdf
e202a358-3f4a17df
16e0dd70-3f4a17df
66df3e9d-a3a14831
b7e2524c-f23d1dea
a6674cf-1e5d42aa
3cd9377c-aed099c4
da89714-4ad60575
64da5c1e-7bc2af31
8982496f-ca7d8d80
b1681d28-1410f10
61832c80-3f4a17df
cc20827f-ca7d8d80
9041608a-3f4a17df
5852bcb0-f23d1dea
9853922b-c200976c
ca05d627-3f4a17df
3e38f260-f8f5001
7c1bc906-6790560b
9def365c-3f4a17df
47e5d3db-3d47f4f4
125b7f68-26e7b859
d442dfb7-41afa35c
9ca1387e-3f4a17df
71ed337-5b96f4bb
1149accc-f23d1dea
4dc30737-b8a5ea08
af59fc20-2599138c
34d450b1-5d0693b2
15d89564-80f9a33e
a582a1b8-ad75ce17
495970ba-e0a3140c
7f7844ec-f9a429c5
3042ad4b-864de28a
ebbb4e0a-ca7d8d80
98be3390-d93a0620
267255c3-f4950e99
249dd49a-28165b59
116c6887-4d2fac87
44827ee5-f23d1dea
88a387d2-f0d95b7c
345b5b61-f23d1dea
edbcf7c5-2d3ce014
5485fc4d-3d47f4f4
93731dca-b4cbfb4e
41f007f9-f23d1dea
9b4c4257-6ad6e56e
43f62d3b-f23d1dea
c992f345-ca7d8d80
165e16d1-3f4a17df
9e5c75f1-4444af57
6872f671-991e1e1
2594bdf4-ed9a47bf
6fa07eb4-ca7d8d80
34d9fc71-f23d1dea
f2fd8aaf-ca7d8d80
4934552d-3f4a17df
2ca9c26b-3f4a17df
2fccc5d5-f23d1dea
7a5ba892-f23d1dea
d1cd70a5-9abb03f9
4ea303a6-4cfc0de5
3d7e3f6a-2eb01455
6e6e0c7e-f23d1dea
95876445-59ecb071
d92562a9-4d2fac87
4da5ae82-91c810ef
dc5b1f29-dc5b1f29
2c1d398c-3f4a17df
cc54eb06-f23d1dea
58a025e3-36e97b2c
5e13f721-24ff7b7b
4932440-d21eb72d
df072bba-ca7d8d80
8576baf1-3f4a17df
51b9b54d-3f4a17df
7345ea6-3f4a17df
344833e9-473e8c2e
3f273a97-25a103a9
4bc337ce-87ea0e5e
d1466cda-f23d1dea
9a2f4e5b-ca7d8d80
494d8760-52325d43
3ac60855-486e2a9c
f296190c-a0af34c0
4442aae2-7158671e
ed1d377-e1cc0f14
12e17bc5-e1cc0f14
75f0f0a0-6bdfffe7
e2b18481-3a9ae350
e7e71889-e1cc0f14
f9e5da91-508355f5
6e3b857e-b94298be
a4f1de9f-3f4a17df
6a51bb09-ca7d8d80
82ebe475-3f4a17df
cc73f8a1-a2d707c6
b4e8892d-f23d1dea
8834fcca-cf4f6ead
3f33c9bd-332ab290

@creis:

Yes! it does! 

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Hello everyone,

First off, I want to say that I'm sorry for being so sloppy in reporting this bug. I'm usually a lot more careful. I also want to thank you all for putting in the time to work on figuring this out.

After comparing and testing  bug 877762 , I would say it's safe to say that this bug and that one are the same. The only thing OOPIFs respond to is keyboard input, not scrolling or clicking. I learned this whilst trying to get Duo 2fa to work, the OOPIF focuses on the "Send push" button automatically. Hitting enter would send the notification and allow me to carry on, even when I couldn't click.

PDF's respond in the same way, though the don't respond to scrolling or touch input, they do respond to scrolling with the keyboard. You can go ahead and merge this bug report into it. 

No problem, thanks for all the info.