New issue
Advanced search Search tips

Issue 851215 link

Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: Jun 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 1
Type: Bug
Team-Accessibility



Sign in to add a comment

Switch Access + Chrome on Android: crashing/temporarily acting like keyboard instead of switch

Project Member Reported by leberly@chromium.org, Jun 9 2018

Issue description

Chrome version:	68.0.3440.14 (Official Build) dev (32-bit)
Android 8.1.0 Security Patch level: June 5, 2018
Accessibility Services version:	6.2.0.199471009 Beta APK
GBoard 7.2.9 version 26720914
Pixel 1 phone signed in with Chromium account (non-corp)
ablenet Blue2 Bluetooth switch

Steps to reproduce:
# Connect Switch and use with Switch Access. I set it up to use Step Scanning to navigate and one switch to select, giving me the most control over generating events. I also chose to use speech output to give maximum verbosity in the log files but this also happens without speech. 

# Navigate to Chrome Beta or Stable and tap to open 
# Navigate through the toolbar icons, passing the menu button to get to the main webpage content. In some cases I had the NTP and in some cases I had https://en.m.wikipedia.org/wiki/Cat, I saw no difference. 
# Once the highlight is on the webpage, scroll through the content using the action menu > scrolling feature. 

# Reboot phone and turn switch off and on to re-pair

# Navigate to Chrome Dev or Canary and tap to open
# Navigate through the toolbar icons, passing the menu button to get to the main webpage content. In some cases I had the NTP and in some cases I had https://en.m.wikipedia.org/wiki/Cat, I saw no difference. 

Expected: same as Beta or Stable
Actual: focus ring goes away, switch starts to act like a keyboard in that pressing the space bar scrolls the page. Wait a few seconds and all of the switch events will eventually "catch up", spoken all at once. Every item in the webpage becomes highlighted per screenshot, attached. 

Guide to attached logcat files: 
Two samples of the error behavior in Dev channel; one in Canary
One sample of error behavior in Dev with voice off (all other tests have voice)
Two samples of the normal behavior in Beta, one in Stable
One sample of the same test done in the settings app, can't repro error behavior at all there. 

 
switchaccesschromenotaccessingwebpage_dev_error.txt
609 KB View Download
switchaccesschromenotaccessingwebpage_dev_error_2.txt
920 KB View Download
switchaccesschromenotaccessingwebpage_canary_error.txt
763 KB View Download
switchaccesschromenotaccessingwebpage_beta_noerror.txt
1.2 MB View Download
switchaccesschromenotaccessingwebpage_beta_noerror2.txt
806 KB View Download
switchaccesschromenotaccessingwebpage_stable_noerror.txt
810 KB View Download
switchaccesschromenotaccessingwebpage_dev_error_speechOff.txt
880 KB View Download
switchaccessSettings_noerror.txt
655 KB View Download
Description: Show this description
Labels: -M68a11ysmoke
I am archiving this bug since further investigation has shown different results. Replacing this bug with 851218
Status: Archived (was: Available)

Sign in to add a comment