Attachment nvda.log added by vgjh2005 on 2014-04-19 06:38
Description:
This is the log for these errors.

Comment 1 by briang1 on 2014-04-19 08:23
I thought there was a ticket for this lack of cursor feedback in chrome, and that it needed an external fix from the authors of the browser.
However the particulare version you mention I do believe has other access issues which do not exist in earlier or the next version of Chrome.

Comment 2 by jteh on 2014-04-19 08:48
The problem with cursor tracking in editable text fields is a bug in Google Chrome. It is fixed for Chrome 36. You can test it now in Chrome Canary.

If you're hearing an NVDA error sound, an error will have been logged. Please reproduce the problem and then provide the NVDA log file as described in LogFilesAndCrashDumps.

Comment 3 by jteh on 2014-07-17 01:29
For some reason, I didn't see that you had already provided a log. My apologies.

As the first issue reported here is fixed in Chrome, I'm morphing this ticket to just cover the second issue.

Technical: The Chrome vbuf is assuming that all objects with the same window handle are IA2 objects, but this isn't the case for input composition/candidates.
Changes:
Changed title from "The characters cannot be browse normally in chrome34." to "Chrome: Exceptions when entering east Asian characters"

Comment 5 by vgjh2005 (in reply to comment 3) on 2014-07-18 04:50
Replying to jteh:
I am sorry for delay. I don't know this ticket is updated. Now, I upload the error log here.Thanks.

Attachment nvda.2.log added by vgjh2005 on 2014-07-18 04:56
Description:
error log about imput eastasian.

Attachment errors log for chrome 36.log added by vgjh2005 on 2014-07-18 05:23
Description:
This is the error log for chrome 36. Thanks.