Bug 423330 - [Accessibility] Voice Over has problems reading editor content [Chrome]
Summary: [Accessibility] Voice Over has problems reading editor content [Chrome]
Status: RESOLVED FIXED
Alias: None
Product: Orion (Archived)
Classification: ECD
Component: Editor (show other bugs)
Version: 5.0   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: 5.0 M2   Edit
Assignee: Silenio Quarti CLA
QA Contact:
URL:
Whiteboard:
Keywords: accessibility
: 423262 (view as bug list)
Depends on:
Blocks:
 
Reported: 2013-12-05 10:36 EST by Silenio Quarti CLA
Modified: 2014-02-21 15:54 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Silenio Quarti CLA 2013-12-05 10:36:05 EST
1) Turn on Voice Over on Mac
2) Open the orion editor with some content
3) Place the caret on the first line and arrow left or right. Note that Voice Over reads the characters correctly.
4) Now move the caret down to second (third, etc) lines. Arrow left or right.

Note that Voice Over reads some other character.
Comment 1 Silenio Quarti CLA 2013-12-05 13:56:08 EST
The problem happens because every line has a "\u200B" character at the end.  This unicode character causes VoiceOver to read the wrong offset.  The zero width space character was used because the regular space character caused the longest line in the editor to wrap in the past (read the comment in the source for more info).   I was not able to reproduce the wrapping problem anymore even with an old version of Safari (5).  I suspect the editor internal structure has changed in a way that the wrapping problem no longer happens.  

This specific problem is fixed by using the regular space:

http://git.eclipse.org/c/orion/org.eclipse.orion.client.git/commit/bundles?id=734f866ac638c3ad8a8a329139a431fd626f4280

Note that this is a problem in Chrome with unicode characters.  If you add Japanese characters to the text buffer. The problem will show up again. There is nothing we can do about this. It has to be fixed by Chrome.  The problem does not happen on Safari.
Comment 2 Silenio Quarti CLA 2013-12-05 13:59:36 EST
The problem does not happen on latest Chrome for Windows (31.0.1650.63 m) with NVDA reader.
Comment 3 Silenio Quarti CLA 2013-12-05 15:51:07 EST
*** Bug 423262 has been marked as a duplicate of this bug. ***