Re: [orca-list] Another Page where Orca gets Stuck

[Steve Holmes <steve holmes88 gmail com>]

I think I will simply paste the bulk of my original message into a new
bug against Orca.  Thanks for the confirmations.  This is a good
example of "Misery makes company"; glad you were able to duplicate the
situations.  I will clarify in the bug that it pertained specifically
to Firefox 4.0 and above.

On Tue, Sep 07, 2010 at 11:29:37PM -0400, Joanmarie Diggs wrote:
> Hey Steve.
>
> I just gave it a quick try using 3.6.8 from Maverick and the 4.0 nightly
> from Mozilla.
>
> > First, go to this link or similar at this site:
> > http://articles.sitepoint.com/article/html-css-beginners-guide/6
> > and get into the body of this article after an h1 heading.  Read down
> > line by line and notice what happens just before each image.  Now
> > here's the kicker.  I was getting stuck while Firefox 4.0 Beta was
> > configured with the automatic loading of images unchecked (turned
> > off).
>
> Confirmed. But I'm only seeing that issue with 4.0; not 3.6.8.
>
> > If I were to use continuous reading, it gets past it OK and
>
> With continuous reading/Say All, we *periodically* position the caret in
> the objects being read. (Basically, doing so keeps the text being
> presented visible for users with low vision.) However, when we're
> controlling the caret and you are navigating, by definition we have to
> reposition the caret in each object being navigated to. So my initial
> guess is that something (dunno what yet) related to setting the caret is
> triggering the bug.
>
> > sometimes I could use the larg object jump key to get me to the next
> > block of text.  
>
> (This tells me that the offending object doesn't have a dead accessible
> nearby. We can't figure out how to get past them. At least not in the
> current code.)
>
> > But if I turn the auto loading of images on, then
> > arrowing down gets me past the pictures.  
>
> Confirmed.
>
> > But then after pressing F6 to get the url for this page, I tried to
> > get back to the page text and then orca seemed to go silent on me and
> > I had to go and restart the program.
>
> Crap. Confirmed.
>
> > Is this another case of the dreaded dead accessibles??
>
> I'm not seeing any.
>
> This is going to take a bit more effort to debug. So.... Make you a
> deal: If you file this information in a new bug report (against Orca), I
> will add it to my high-priority to-do list. After I debug it, we can
> discuss where the problem is and how I reached that conclusion. Ok?
>
> Thanks for all your work in this area!
> --joanie