Issue metadata
Sign in to add a comment
|
ChromeVox reads unicode whitespace in chrome's dialogs
Reported by
jleedev@gmail.com,
Apr 23 2018
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; CrOS armv7l 10323.67.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.209 Safari/537.36 Platform: 10323.67.0 (Official Build) stable-channel daisy Steps to reproduce the problem: 1. Sign in to guest mode 2. Press Ctrl+Alt+Z to turn on spoken feedback 3. Press Ctrl+S What is the expected behavior? The "Save file as" dialog should be read. What went wrong? I get to hear about "zero width no break space". This refused to show up in a screenshot, so here's a photo. Did this work before? N/A Chrome version: 65.0.3325.209 Channel: stable OS Version: 10323.67.0 Flash Version: Credit for finding this goes to my toddler.
,
Apr 29 2018
,
Apr 29 2018
Hi, I tested this on my current dev build 68.0.3410.0 and I can reproduce partially. It does start reading "Zero ..." while the "Save file as" dialog is opening, but once it loads it reads "File name Edit text", so it sounds like: "Zero file name, edit text." which isn't ideal. Your screenshot suggests that there was an error when loading the "Save file as" dialog which never finished loading. I'll try to workaround this reading "Zero width no break space", and/or report to ChromeVox team. Lastly thanks for sharing the toddler detail, it put a smile on my face. :-)
,
Apr 30 2018
,
Apr 30 2018
I've reported to ChromeVox team too: crbug.com/838020 But I'm working around on File Manager application.
,
May 8 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/10dc10e778bdab3a0019aba329fa419be1f464bd commit 10dc10e778bdab3a0019aba329fa419be1f464bd Author: Luciano Pacheco <lucmult@chromium.org> Date: Tue May 08 03:13:58 2018 Remove unicode char zero width space from title This fixes the issue where ChromeVox was reading "Zero width no break space" while File Manager or "Save as" dialog was loading. This unicode char was added by the following patch, but without a clear reason: https://chromium.googlesource.com/chromium/src/+/9485ad7b2a08306e23e9980d73a0eaa73da98610%5E%21/#F10 Bug: 835789 Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation Change-Id: I7cc698071ab0c42df4f208e92a2c3cf0fb15cb0a Reviewed-on: https://chromium-review.googlesource.com/1034415 Reviewed-by: Naoki Fukino <fukino@chromium.org> Reviewed-by: Sasha Morrissey <sashab@chromium.org> Commit-Queue: Luciano Pacheco (SYD) <lucmult@chromium.org> Cr-Commit-Position: refs/heads/master@{#556666} [modify] https://crrev.com/10dc10e778bdab3a0019aba329fa419be1f464bd/ui/file_manager/file_manager/main.html
,
May 8 2018
The patch submitted on the previous comment fixes the issue. It'll take some time to be finally available to final users, probably on version 69. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by weifangsun@chromium.org
, Apr 27 2018