ChromeVox: Chrome page becomes unresponsive or ChromeVox dies

Dulciane / google-axs-chrome

Automatically exported from code.google.com/p/google-axs-chrome

0 stars 0 forks source link

ChromeVox: Chrome page becomes unresponsive or ChromeVox dies #40

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago

Windows 7 8x86
ChromeVox 1.16.0

Chrome 16 beta
Google.com
type "ChromeVox";
TAB to search button and ENTER;
ChromeVox+N, H to go to next heading several times rapidly

Expected: ChroemVox to be able to quickly navigate, read, and work with all 
headings.
Actual: After about the fifth or sixth heading, ChromeVox will go absolutely 
silent. 

Notes: 
1) Launching NVDA and checking Chrome, it shows that the page has become 
unresponsive with options to kill page or wait. Selecting wait does no good and 
kill pages works, but repeating the above steps result in same issue.
2) chrome://crashes doesn't show any crash log for this particular event, but I 
have several crash logs/ID's for last week and previous events.

Original issue reported on code.google.com by KevinCha...@gmail.com on 23 Nov 2011 at 10:57

GoogleCodeExporter commented 8 years ago

Chrome 17 Canary
Google.com;
type "ChromeVox";

Expected: ChromeVox to echo typed characters
Actual: nothing, absolute silence.

TAB;

Expected:  ChromeVox to navigate to and read Google Search button
Actual: Nothing, absolute silence

Notes: Launching NVDA, checking Chrome, and it shows that the page is still 
responding, but ChromeVox just won't work with Google.com

Original comment by KevinCha...@gmail.com on 23 Nov 2011 at 11:00

GoogleCodeExporter commented 8 years ago

Do you think you could send me/the list your crash IDs that you mentioned you 
had for last week?

Original comment by rshea...@google.com on 30 Nov 2011 at 7:35

GoogleCodeExporter commented 8 years ago

Oh also, for the comment you made on this bug about ChromeVox not echoing typed 
characters on Google.com - was that for Windows 7 too?

Thanks so much for filing these issues!

Original comment by rshea...@google.com on 30 Nov 2011 at 7:38

GoogleCodeExporter commented 8 years ago

Oops, forgot to check the box that would notify you I changed this issue. Just 
to summarize:
1) Do you think you could send me/the list your crash IDs that you mentioned 
you had for last week?
2) For the comment you made on this bug about ChromeVox not echoing typed 
characters on Google.com - was that for Windows 7 too?

Original comment by rshea...@google.com on 30 Nov 2011 at 7:42

GoogleCodeExporter commented 8 years ago

Yes, ChromeVox not echoing typed characters is for Windows 7.
Crash IDs:
f069cc5d69e48717
e6694a5370991363
ba168a8f48a370c4
81017cdb327b305c
8344dbb0668d96d5
a9df641a1f9e5e11
fb6a8701825f4a26
74621bf97c435d46
b0588423b3034e95
43a9ec04bb8410d0
1fd25c9f8b75dd2f
04416eec99e284cf

Original comment by KevinCha...@gmail.com on 30 Nov 2011 at 8:03