Re: [orca-list] clickable item strangeness

[Joanmarie Diggs <jdiggs igalia com>]

Hmmmm. I just made a change in my local copy of Orca to see if I could
improve the situation by re-requesting the coordinates to be clicked
on. But I always get the same coordinates. Thus that doesn't appear to
be the problem. At least not for my test cases.

Therefore it would be helpful to see a full debug.out -- or perhaps a
couple. For instance, a single debug.out in which you get the message
"not found". And then a different debug.out in which Orca doesn't
complain, but also doesn't click on the desired object.

Thanks again!
--joanie

On Fri, 2020-10-09 at 11:37 +0200, Joanmarie Diggs wrote:
> If it fails the first time but not the second, it could have
> something
> to do with Chromium itself, which gives an imprecise location of
> objects the first time. I'll see if I can improve the situation on
> that
> front.
>
> In the meantime: A bisect is only useful to find regressions. Are you
> saying that there was a point where Orca always reliably clicked on
> clickables in Chromium? Or that it has always been flaky?
>
> --joanie
>
> On Thu, 2020-10-08 at 12:45 -0400, Kyle via orca-list wrote:
> > Trying to activate clickable items using Chromium 85.0 and orca
> > master, 
> > I am noticing that sometimes I have to simulate a click on the item
> > a 
> > second time before it activates. I'm not trying to do it from the
> > list 
> > of clickable items, but from the simulated mouse click (keypad
> > slash) 
> > function. At other times, the item is reported as "not found,"
> > although 
> > I'm not sure in those situations whether it is actually clicked ...
> > it 
> > does seem as though it does eventually get clicked, but I can't say
> > for 
> > sure. I'm not entirely sure whether this bug is only affecting
> > Chromium 
> > or if Firefox is also affected, as I have only needed to do this 
> > frequently using Chromium. I have noticed this since I started
> > using 
> > Chromium on a regular basis, but thought it may have been related
> > to 
> > some of the slowness that I had experienced intermittently in
> > older 
> > versions of Orca, and especially the huge performance regression I 
> > helped find in later versions, but even as well as it is performing
> > now, 
> > I still see this behavior. Hopefully we can track this one down as
> > well, 
> > although this may be somewhat more difficult, as I don't have a
> > known 
> > good commit to start a bisect. Thanks very much for any help.
> >
> > ~Kyle
> >
> > _______________________________________________
> > orca-list mailing list
> > orca-list gnome org
> > https://mail.gnome.org/mailman/listinfo/orca-list
> > Orca wiki: https://wiki.gnome.org/Projects/Orca
> > Orca documentation: https://help.gnome.org/users/orca/stable/
> > GNOME Universal Access guide: 
> > https://help.gnome.org/users/gnome-help/stable/a11y.html
>
> _______________________________________________
> orca-list mailing list
> orca-list gnome org
> https://mail.gnome.org/mailman/listinfo/orca-list
> Orca wiki: https://wiki.gnome.org/Projects/Orca
> Orca documentation: https://help.gnome.org/users/orca/stable/
> GNOME Universal Access guide: 
> https://help.gnome.org/users/gnome-help/stable/a11y.html