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

[Steve Holmes <steve holmes88 gmail com>]

Yeah, I usually run the browsers with loading of images turned off,
figuring it should save load times and all that and since they don't
specifically mean anything to me.  But I thought it curious if I were
to turn them on to see what would happen.  The blockage always seemed
to happen when the text referred to some image below in most cases.  I
probably would have never given it a thought to turn images on.

On Wed, Sep 08, 2010 at 09:15:53AM +0200, Mallory van Achterberg wrote:
> Hm, I noticed after two images (but not all of them) there's some bit of 
> strange Google Javascript code right afterwards.  Could it possibly be 
> involved?
> Firefox is the only browser I know of who collapses images who don't load
> (maybe this explains why loading the images makes a difference?).
>
> -Mallory
>
> 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
> >
> > _______________________________________________
> > 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