GNOME Bugzilla – Bug 741354
Last line of textareas isn't spoken by Orca
Last modified: 2015-05-18 13:28:17 UTC
To reproduce this: 1. Open the "Enter Bug" page for entering Orca bugs. 2. Write something like "This is a test." and press enter. 3. Write something like "This is another text." and do not press enter. Go up with the up arrow key and go back down with the down arrow key. You don't hear anything. 4. The only way to fix this is to go up twice. That means to move up to the line above twice.
This will be fixed in master soon as part of the web document work I'm currently doing.
*** Bug 736604 has been marked as a duplicate of this bug. ***
Should be fixed in master. Please verify.
Created attachment 303498 [details] This is a debug.out file with shows a result with the committed fix Hi Joanie, Now, Orca speaks all lines right, but I founded a resulted issue. Testcase: 1. In any Bugzilla multiline edit box or a Thunderbird message compose window paste following text: test1 test2 2. Press CTRL+HOME, and press one time the down arrow key. Orca this situation producing the expected result, speaks right the test2 message. 3. Press again the down arrow key. Expected result: Orca not need speaks anything, because you landed the last line. Actual result: Orca again speaks the test2 message. If this situation I press up arrow key, I hear right the test1 message. If press down arrow key when Orca spokened the test1 message, I right hear the test2 message. When after the second repeat test I press down arrow key, Orca not speaks again right the test2 message. Attila
I can reproduce that, but I don't think it's a bug. Here's the situation: Whether Orca is running or not, the Gecko behavior is: 1. Ctrl+Home moves you to the beginning of the line with "test1" 2. Down arrow moves you to the beginning of the line with "test2" 3. Down arrow moves to you the end of the line with "test2" So you are moving. And Orca should present that. But the "new" line is "test2". And when you down arrow, Orca should present the line you arrowed to, right? Having said that, if you think that's a bug, please open a new issue for it. Based on your confirmation (thanks!), I'm going to close this bug as FIXED.