Issue metadata
Sign in to add a comment
|
Full Screen magnifier crashes TTS settings page on first load |
||||||||||||||||||||||||
Issue descriptionGoogle Chrome OS 68.0.3400.0 (Official Build) canary (64-bit) Eve Does not repro with docked magnifier, only with full screen magnifier Steps to repro: # Powerwash or reimage to get Chromebook in a state such that it never had full screen magnifier on before # Enable Experimental Accessibility flag in chrome://flags # Navigate to Settings > Manage accessibility features > Text To Speech voice settings page # Open fullscreen magnifier from Status bar > Accessibility Expected: page remains the same Actual: this page crashes (I could repro this 3 times in a row) Note that if you follow the above steps except going to the main settings page when enabling full screen magnification, it does not crash. Also, if you enable it on the main settings page and navigate to the Manage accessibility features > Text To Speech voice settings page, it does not crash. If you turn on full screen magnifier on the TTS voice settings page for the second or more time, it does not crash.
,
Jun 28 2018
Back to leberly@ to help with a repro
,
Jul 18
,
Jul 20
Google Chrome 69.0.3494.0 (Official Build) dev (64-bit) Firmware Version Google_Celes.7287.92.104 Flipping to WontFix, unable to reproduce using these steps: # Powerwash # Navigate to Settings > Manage accessibility features > Text To Speech voice settings page # Enable Fullscreen magnifier using status bar > Accessibility > Fullscreen magnifier (perhaps it is there for me because I have used these features before while signed into my Chromium account.) # Accept prompt for turning on for the first time Does not crash Before powerwashing, I also tried using the new shortcut keys ctrl + search + m and accepted the prompt for using for the first time, and it did not crash. I didn't think I had used the fullscreen magnifier on that machine before but I wanted to be really sure so I did the steps above.
,
Aug 7
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by katie@chromium.org
, Jun 26 2018