Re: [orca-list] Orca not accessing the message content area in thunderbird after viewing one message

[hackingKK <hackingkk gmail com>]

I get the same problem as Michael pointed out.
I use orca 2.91.92 and thunderbird 3.1 (please some one tell me how to 
migrate to thunderbird 3.1.8 ).
Further more, this unreadability also happens if I do a right click on a 
typo and correct the spelling.
happy hacking.
Krishnakant.

On 24/05/11 04:47, Michael Whapples wrote:
> Hello,
> On trying some more I find if I cursor left and right speech tells me 
> what I am cursoring over and pressing the key to read all will speak 
> the message content. Also flat review will see the message content, 
> but obviously only can see what is visible.
>
> However, up and down cursor does not read the content or move the 
> cursor. Also Braille does not show the message content, even when 
> using read all. Braille sometimes just shows a blank line, but most of 
> the time the window title bar.
>
> Does any of this help track down the bug?
>
> Michael Whapples
> On 05/23/11 23:15, Steve Holmes wrote:
> > wWhat would happen if you back out at-spi2-core and run with the
> > production version and the git version of Orca? I'm thinking in terms
> > of isolating the problem to a given package.  Also when Mike Gorst
> > mentioned the at-spi2 stuff, he also mentioned at-spi2-atk and
> > possibly pyatspi2 so I'm not sure if all of these guys have to be
> > built every time a fix comes out; I hope not.  I'm not on my home
> > machine right now so can't follow up on these questions myself right
> > now.
> >
> > On 5/23/11, Michael Whapples<mwhapples aim com>  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