After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 736604 - Orca some time skyp last line spokening in focus mode
Orca some time skyp last line spokening in focus mode
Status: RESOLVED DUPLICATE of bug 741354
Product: orca
Classification: Applications
Component: speech
3.13.x
Other Linux
: Normal normal
: ---
Assigned To: Orca Maintainers
Orca Maintainers
Depends on:
Blocks:
 
 
Reported: 2014-09-13 06:05 UTC by Hammer Attila
Modified: 2015-03-12 12:16 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Debug file (448.70 KB, application/octet-stream)
2014-09-13 06:05 UTC, Hammer Attila
Details
Thunderbird related debug.out file (1.09 MB, application/octet-stream)
2014-09-13 06:12 UTC, Hammer Attila
Details
Debug file with Orca master branch version related (323.03 KB, text/plain)
2015-03-12 09:03 UTC, Hammer Attila
Details

Description Hammer Attila 2014-09-13 06:05:24 UTC
Created attachment 286103 [details]
Debug file

Dear Joanie,

If Orca have in focus mode, Orca some time skyp last line spokening if the previous line is not a blank line. This problem affecting up or down arrow key navigation, both Firefox and Thunderbird.
Firefox related affected the text formfield element, in Thunderbird affected the message body part in message compose window or the reply dialog.
Testcase with Firefox related.
1. Goto Bugzilla, and try opening a new report.
2. In description field type four line, separate with enter keys. Do not put a blank line before lines.
3. Try using more time with up or down arrow keystrokes. Me some time Orca not spokening the last line content.

My environment related informations:
OS: Ubuntu 14.04
Orca version: latest master branch
Affected Orca branches: master, gnome-3-14
Firefox version: 32.0
Thunderbird version: 31.1.0

Attila
Comment 1 Hammer Attila 2014-09-13 06:12:58 UTC
Created attachment 286104 [details]
Thunderbird related debug.out file

Testcase with Thunderbird related:
1. Launch Thunderbird, and press CTRL+N keystroke.
2. Goto the message body part.
3. Paste following text:
foods
apple
cheese
potato
brad
4. Press CTRL+HOME keystroke, and do more ciclical up or down arrow navigation. Usual the issue happening if I moving betveen and the fourth and the third line with up or down arrow keys.
The debug file will be you see I do more line navigation operations. Some time Orca spokenng all lines, some time not, and some time skyp only the two last line spokening.

Attila
Comment 2 Hammer Attila 2014-09-13 06:24:07 UTC
The issue is reproducable if the text formfield or Thunderbird message body containing three text lines, and if the last line is blank.
This situation when I doing more ciclical up or down arrow key navigation Orca usual skyp the last non blank line and the last blank line spokening. If the last line is blank, and checked the speak blank lines check box in Orca preferences dialog/speech page, Orca need spokening the "blank" translatable text. The text box is checked by default.

Attila
Comment 3 Joanmarie Diggs (IRC: joanie) 2014-09-13 07:04:56 UTC
I can reproduce this, but I also see the following in your debug.out and mine:

FAIL: Bad results for text at offset 30 for [document frame | about:blank] using TEXT_BOUNDARY_LINE_START:
      String: 'brad', Start: 26, End: 30.
      The bug is the range returned is outside of the offset.
      This very likely needs to be fixed by Mozilla.
HACK: Attempting to recover from above failure.
      Returning: '' (30, 31) 

What the above means is Orca asked for the line which starts at offset 30 and should end, well, after offset 30. And Thunderbird's answer is, "The line which starts at offset 30 starts at offset 26 and ends at offset 30." Clearly that's a bug in Thunderbird or Gecko. Orca's hack to recover is not unreasonable, and it keeps Orca from looping and repeating. But if Thunderbird or Gecko is giving bogus information, there may be other points of failure.

So.... Given that this is at least in part, if not entirely, a Thunderbird or Gecko bug, and given that I've already filed a number of bugs similar to this one for Mozilla to fix, let's keep this one open for now. I'll triage it further later and see if it's already covered by one of the bugs I already filed.
Comment 4 Hammer Attila 2014-09-13 07:39:30 UTC
Hi Joanie,

I agree with you wrote. If this issue is a Gecko bug, better with Mozilla developers fixing this issue if this is possible and not an optimal solution to doing an Orca hack. Now cleaned lot of oldest Orca hacks the master branch and gnome-3-14 branch versions. Now wonderful possible using Firefox with Orca master and gnome-3-14 branch versions again, not happening text skippings, etc.
I don't no only one thing:
If the Gecko toolkit get the proper fix from Mozilla developers, popular distros will get the proper update (Ubuntu long term supported Trusty release, Arch, Debian Jessie, Fedora, etc)?
Firefox is more often upgrading with newest version, but how often upgrading the main Gecko toolkit with newest version with future containing the proper fix? Thunderbird very long time not get major version update, only minor updates (from 24.x series has more years before happened the 31.0 release change).
For example with Ubuntu Trusty the A11y stack components will not get updates the official repo, still have the 3.10.x versions. So, if anybody want using the latest wonderful working Orca release, need compiling from source the future 3.14 release.

Attila
Comment 5 Hammer Attila 2015-03-12 09:03:17 UTC
Created attachment 299156 [details]
Debug file with Orca master branch version related

Hi Joanie,

I attaching a debug.out file with orca master branch version related.
Final reported this issue with Mozilla developers, or you oldest time opened a report this issue related?

Attila
Comment 6 Joanmarie Diggs (IRC: joanie) 2015-03-12 12:16:23 UTC
I'm going to make this a duplicate of 741354. As I stated there, I have a workaround which is part of a bigger commit which I hope to merge soon.

*** This bug has been marked as a duplicate of bug 741354 ***