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 426687 - [Pending] Orca should only speak entry text when arrowing Up/Down in an entry in Firefox
[Pending] Orca should only speak entry text when arrowing Up/Down in an entry...
Status: RESOLVED FIXED
Product: orca
Classification: Applications
Component: general
2.19.x
Other All
: Normal normal
: ---
Assigned To: Orca Maintainers
Orca Maintainers
Depends on:
Blocks: 404403
 
 
Reported: 2007-04-05 17:37 UTC by Joanmarie Diggs (IRC: joanie)
Modified: 2007-04-13 16:48 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Joanmarie Diggs (IRC: joanie) 2007-04-05 17:37:14 UTC
As discussed in the comments of bug #423198, it has been decided that when using Up and Down Arrow to examine the contents of a multi-line entry (such as the Description field in bugzilla), Orca should only speak text in the entry.  Currently it will also speak any text that is on the same line but outside of the entry.  This behavior is confusing when trying to read/edit the entry text.

As Mike specified via phone conversation, when one is not in the entry, Orca should speak any text that is in the entry and on the same line.  In addition, when one is at the beginning of the entry, pressing Up Arrow should continue to move the user outside of the entry and to the previous line.  Likewise, when one is at the end of the entry, pressing Down Arrow should continue to move the user outside of the entry and to the next line.

Mike:  I assume that the braille displayed should parallel the speech.  In other words, when inside of an entry, Orca will only speak and will only braille text that is inside of the entry.  If I'm wrong about that, please let me know.  Thanks!!
Comment 1 Joanmarie Diggs (IRC: joanie) 2007-04-09 23:53:36 UTC
The fix for bug 426684 seems to solve this as well.
Comment 2 Mike Pedersen 2007-04-13 16:48:02 UTC
agreed This problem has been fixed in our software repository. The fix will go into the next software release. Thank you for your bug report.