I think the ARC++ explore by touch issue should be fixed in b/112473547. Does it still happen in canary? Shrija, can you check?

That's a change submitted at https://chromium-review.googlesource.com/1262641 in 71.0.3576.0, but it has a corresponding ARC++ change and I'm not sure when that rolled out.

Another user reported the problem in the Chromebook Help forum, cave device.
https://support.google.com/s/community/forum/465605/thread/616826
I have asked for version info.

I am not able to repro the 2nd part of issue I.e. "Enabling Select-to-speak causes Settings Crashes" for the below version in Canary Channel:

Google Chrome:72.0.3618.0 (Official Build) canary (64-bit)
Revision: 473cb3615ccd757dbfd816963e699299a0732b59-refs/branch-heads/3618@{#1}
Platform: 11298.0.0 (Official Build) canary-channel samus
Firmware Version: Google_Samus.6300.276.0
ARC:5143797
JavaScript:V8 7.2.391
User Agent:Mozilla/5.0 (X11; CrOS x86_64 11298.0.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3618.0 Safari/537.36
Steps to Repro:
1. Enable select-to-speak in accessibility settings
2.Enter chrome://settings/display page
3.Use touch screen to select the text you want to be read aloud
Expected: Allows text to be selected using Touch screen  and Reads aloud the selected text
Actual: Works as expected

I would work on the 1st half of the bug "Enabling Select-to-speak disables touch on Android" and update.

Tried to repro the first half of the bug "Enabling Select-to-speak disables touch on Android", 

However not able to repro as when I selected an app on android, chrome crashed!

Google Chrome:72.0.3618.0 (Official Build) canary (64-bit)
Revision: 473cb3615ccd757dbfd816963e699299a0732b59-refs/branch-heads/3618@{#1}
Platform: 11298.0.0 (Official Build) canary-channel samus
Firmware Version: Google_Samus.6300.276.0
ARC:5143797
JavaScript:V8 7.2.391
User Agent:Mozilla/5.0 (X11; CrOS x86_64 11298.0.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3618.0 Safari/537.36
Steps to Repro:
1. Enable select-to-speak in accessibility settings
2.Goto Playstore and select an app
3.Click on the app
Expected: Allows user to select the app using Touch screen and Reads aloud the selected app text to the user
Actual: Chrome crashes

Note: Tried to repro the above without Select-to-speak and it works as per expected!

Note that the user reports mainly involve trying to run an already-installed Android app.

1. Install various Play Store apps
2. Note that they run properly
3. Turn on Select-to-speak
4. Try to run the installed apps
5. Try to open Settings
6. Try to use the touchscreen

I reproduced the explore by touch in ARC++ part of the bug on Beta channel:
Chrome: 71.0.3578.73
ARC: 5144383
Chrome OS: 11151.46.0

I could not reproduce the explore by touch ARC++ bug in the Dev channel:
Chrome: 72.0.3618.0
ARC: 5149218
Chrome OS: 11301.0.0

Therefore I think the ARC++ part of this did get fixed in a recent build. Try switching to the Dev channel or wait for M72 to arrive in Beta in the next few weeks to get the fix.


I did not reproduce the settings crash in either channel. Do you have any more information about how to reproduce the settings crash?

Marking as fixed because the touch stuff is fixed, and there's no new info on the settings crash. Please file a new bug for the settings crash if it occurs again.