Re: [orca-list] On Github, orca doesn't follow anchor

[Shérab <Sebastien Hinderer ens-lyon org>]

Samuel Thibault (2018/06/14 10:29 +0200):
> Shérab, le jeu. 14 juin 2018 10:24:14 +0200, a ecrit:
> > Samuel Thibault (2018/06/14 10:17 +0200):
> > > Shérab, le jeu. 14 juin 2018 10:07:43 +0200, a ecrit:
> > > > 3. Click on the "L" of "L1" with the corresponding cursor routing key --
> > > > nothing happens.
> > > >
> > > > 4. Press Enter (no matter which keyboard) -- nothing happens
> > > >
> > > > 5. Press the same routing key as in 3 -- it works and brings to the
> > > > right part of the page.
> > > >
> > > > Is there anything else I can try?
> > >
> > > Could you also make a sighted person check exactly when the physical
> > > screen jumps to the anchor?
> >
> > Yeah! On-screen it changes at step 3! :(
>
> Ok, so that might be why the enter key does nothing: it's already on
> the target, which is mere text and thus doesn't do anything on pressing
> enter. So it's when using cursor routing keys that braille doesn't get
> an update. I'll submit a bug report against orca for that particular
> case.

Thanks. I think it's indeed important, because, if I understand things
correctly, if the anchor would be the second link on the line, say, then
it would not be selected by default and Enter would not follow that
link. Am I correct here?

Shérab.