Re: [orca-list] Orca not accessing the message content area in thunderbird after viewing one message
- From: Mike Gorse <mgorse alum wpi edu>
- To: orca-list gnome org
- Subject: Re: [orca-list] Orca not accessing the message content area in thunderbird after viewing one message
- Date: Tue, 24 May 2011 17:40:52 -0400 (EDT)
Hi Michael,
Does pressing tab followed by shift-tab make the cursor keys start working
again for you? I see the same result if I press enter as if I press
ctrl-o--I can't cursor immediately but can if I tab around, whether I'm
using AT-SPI1 or AT-SPI2. I'm wondering if I'm seeing the same bug that
you're seeing. Either way, a debug.out might be useful. I'm noticing
that Orca is seeing a document:load-complete but not anything
focus-related, and perhaps it is expecting a focus event.
-Mike
On Tue, 24 May 2011, Michael Whapples wrote:
Hello,
I just press enter on the message in the message list.
Michael Whapples
On 01/-10/37 20:59, Mike Gorse wrote:
Hi Michael,
What hotkey are you pressing to open a message?
I've installed 3.3a3, and I'm seeing what seems like a bug where, if I
press ctrl-o to open a message, Orca doesn't read anything if I try to
cursor around. If I press tab and shift+tab, I am then able to use the
cursor keys to read the message. This happens with both AT-SPI 1 and
AT-SPI 2 and seems unrelated to whether or not another message was opened
previously, so it doesn't sound like the same bug that you are reporting.
Also, it doesn't happen for me with 3.1.8, although there is a delay of
several seconds when I press ctrl+w with AT-SPI2 (but not with AT-SPI 1).
Thanks,
-Mike
On Mon, 23 May 2011, Michael Whapples wrote:
Hello,
I am using thunderbird 3.3a3 and orca from git (pulled lunchtime today)
and at-spi2-core from git (again lunchtime today). I find that when I view
one message, any further viewing of a message (not necessarily the same
message) orca just will not access the content of the message body. This
seems to also extend to writing a message as well. The only way to work
around this is to restart orca, which gets a bit much as it needs to be
done after viewing every message.
I suspect it might be an at-spi2-core issue, as I think I observed it just
before I updated orca but I cannot quite be sure on that.
Has anyone else noticed this? Anyone else got more information on what the
issue is and if there is a better fix than having to restart orca?
Michael Whapples
_______________________________________________
orca-list mailing list
orca-list gnome org
http://mail.gnome.org/mailman/listinfo/orca-list
Visit http://live.gnome.org/Orca for more information on Orca.
The manual is at
http://library.gnome.org/users/gnome-access-guide/nightly/ats-2.html
The FAQ is at http://live.gnome.org/Orca/FrequentlyAskedQuestions
Netiquette Guidelines are at
http://live.gnome.org/Orca/FrequentlyAskedQuestions/NetiquetteGuidelines
Log bugs and feature requests at http://bugzilla.gnome.org
Find out how to help at http://live.gnome.org/Orca/HowCanIHelp
_______________________________________________
orca-list mailing list
orca-list gnome org
http://mail.gnome.org/mailman/listinfo/orca-list
Visit http://live.gnome.org/Orca for more information on Orca.
The manual is at
http://library.gnome.org/users/gnome-access-guide/nightly/ats-2.html
The FAQ is at http://live.gnome.org/Orca/FrequentlyAskedQuestions
Netiquette Guidelines are at
http://live.gnome.org/Orca/FrequentlyAskedQuestions/NetiquetteGuidelines
Log bugs and feature requests at http://bugzilla.gnome.org
Find out how to help at http://live.gnome.org/Orca/HowCanIHelp
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]