[orca-list] An interesting issue with Orca 3.2 and Gedit 3.2
- From: Hammer Attila <hammera pickup hu>
- To: orca-list gnome org
- Subject: [orca-list] An interesting issue with Orca 3.2 and Gedit 3.2
- Date: Wed, 05 Oct 2011 06:18:29 +0200
Hy,
I found an interesting issue with Orca 3.2 and Gedit 3.2 improvement,
with I am not sure is an Orca bug or a general bug for Gedit Text Editor
3.2 version:
When I launch any method with Gedit, and for example typing text, Orca
doesn't spokening arrow keys operation results. If I switch an another
application and switch back Gedit, the edit box is focused, and all
cursor movement keys Orca spokening the proper result. I see similar
result for example I simple opening the menu bar and close the menu bar.
Before this task cursor movement operations result Orca not spokened and
not presenting the braille display.
If I opening a file for example with gedit text.txt command, I see
similar result after the new file is opened. I experienced similar
results after I opened a new document with CTRL+N key combination.
Perhaps the presented edit box is not focused in Gedit, or the caret is
not enabled by default? Anybody confirming this result if not using Orca?
Reproducation steps:
1. Open for example a terminal.
2. Open a text file for example with following command:
gedit text.txt
3. Try moving line by line with Up or Down arrow keys. The actual line
is highlighted?
If I opening for example an another file with file open dialog, the
problem is repeating always after all file open operation.
Temporary I reported this issue with Orca related, and attached a
debug.out file with following report:
https://bugzilla.gnome.org/show_bug.cgi?id=659454
Attila
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]