Issue metadata
Sign in to add a comment
|
Problem with Chromevox Find Command
Reported by
coleyeva...@gmail.com,
Jun 21 2017
|
||||||||||||||||||||||||
Issue descriptionMode: force_next Version: 59.0.3071.91 Reproduction Steps: 1. In a webpage, press ctrl+f for find. 2. Type a search string and then press enter, or tab to the "next" button. 3. Chromebox gives no indication that text has been found, even if the text exists in the webpage. Even when you press the "close" button, the cursor is where it was before you initiated the find command.
,
Aug 7 2017
You can also use Search+Slash to use the ChromeVox find in page, but leaving this bug open and available to think about how to make the Ctrl+F experience better and more clear for ChromeVox users.
,
Aug 8
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Sep 7
Is this still a problem?
,
Sep 7
Added support at some point after this bug was filed. ChromeVox also has "Search+/" (its own find in page) command. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by pbath...@chromium.org
, Jul 6 2017Status: Untriaged (was: Unconfirmed)