GNOME Bugzilla – Bug 416964
Orca needs better handling for non-breaking space characters in Firefox
Last modified: 2007-03-14 21:06:18 UTC
It seems that Orca is treating the non-breaking space character as something other than a space. Thus when moving word by word, it seems that we are moving further than we should and that Orca is reading more than it should. In addition, because Gecko treats the non-breaking space character as a space, if Gecko is controlling the caret movement seems more logical (to me), but Orca does not read the word at the caret; instead it reads (repeats) the entire string. Try using Orca to read the test case (to be attached) word by word, first with Orca controlling the caret then with Gecko controlling the caret.
Created attachment 84366 [details] aforementioned test case
I'd guess a non-breaking character check needs to be added to default.py:isWordDelimiter. isWordDelimiter may also need to be rewritten to work with unicode internally instead of UTF-8 (right now, it works with UTF-8 and converts any incoming unicode to UTF-8 before processing it). See the following URL for more information: http://en.wikipedia.org/wiki/Non-breaking_space
Created attachment 84583 [details] [review] Patch to add no break space character to word delimiter check This patch adds the no break space character to the word delimiter check. Seems to work. Joanie, can you please verify?
Verified. Thanks!!
Thanks! Committed and closing as FIXED.