Comment 1 by James Teh <jamie@... on 2014-07-03 04:46
In [174a1fa]:

Extend our current hack to support Mozilla rich text editing to work in more places.

Previously, it only worked when the editable area had a role of document and didn't have a tree interceptor. Now, it works in any editable area that has the editable and focusable states.
Re #4244.

Comment 2 by James Teh <jamie@... on 2014-07-03 04:46
In [88a12d9]:

Merge branch 't4244' into next

Incubates #4244.

Changes:
Added labels: incubating

Comment 3 by ateu on 2014-07-03 11:35
Hi,

Which aps will be benefited with this change?

Comment 4 by jteh on 2014-07-03 23:00
It is relevant to rich text editing in Mozilla based apps such as Firefox. It should help with various editors on the web, but it was primarily intended to provide partial support for the new braille mode in Google Documents (which is currently disabled for Firefox).

Comment 5 by nvdakor on 2014-07-06 12:44
Hi,
A Korean user who uses next snapshot reports:
In Mozilla applications such as in Firefox, when input language is set to Korean, NVDA keeps announcing "has auto-complete" each time Korean character is entered. This does not happen for English text.
STR:

1. Start Firefox with Korean input method installed.
2. Once the home page opens, go to address bar (Alt+D).
3. Type a text, for example, "javascript" in both English and Korean (in Korean, with input mode set to native input via right Alt key, type wkqktmzmflvmxm).
   Expected: When typing text, NVDA doesn't say "auto-complete" each time new characters are entered. This is when typing English text.
   Actual: When typing each Korean character, NVDA announces "has auto-complete". For exampl, the user sent a log to the users group and the translation is thus:

input: w
Output: Has auto-complete, W
Input: k
Output: has auto-complete, wk
Input: q
Output: has auto-complete, wkq
...}
Specs:
* NVDA latest next snapshot.
* Firefox nightly.
The user believes that recent hack to support rich edit fields in Mozilla applications may be triggering this issue. Thanks.

Comment 7 by James Teh <jamie@... on 2014-07-07 10:14
In [47708f6]:

Fix continual announcement of Mozilla (and perhaps other) editable areas when typing in Korean and other east Asian languages.

Caret events are fired whenever a character is typed. However, when input composition is in progress, we fake the focus. The caret event was causing the focus to be bounced out of the input composition object back to the editable area every time a character was typed.
Fix this by ignoring these caret events when the focus is not an IAccessible.
Re #4244.

Comment 8 by James Teh <jamie@... on 2014-07-07 10:14
In [48c4d6a]:

Merge branch 't4244' into next

Incubates #4244.

Comment 9 by James Teh <jamie@... on 2014-08-05 00:44
In [09dd036]:

Slight improvements to some rich text editors in Mozilla Firefox.

This just improves our current hack and is still by no means a good solution, but it at least allows better access to some editors until we get proper support for Mozilla rich text editing.
Fixes #4244.

Changes:
Removed labels: incubating
State: closed

Comment 10 by jteh on 2014-08-05 00:45
Changes:
Milestone changed from next to 2014.3