Re: [orca-list] Google chrome and orca

[Didier Spaier <didier slint fr>]

Hello John,

81.0.4033.2 should work correctly as I have 81.0.4021.2 which is already
good enough.

I wrote a startup script /usr/bin/chrome with this content:

#!/bin/sh
export ACCESSIBILITY_ENABLED=1
/opt/google/chrome-unstable/google-chrome-unstable --enable-caret-browsing --force-renderer-accessibility

Then indeed:
chmod 755 /usr/bin/chrome

HTH.

Best,

Didier

Le 27/01/20 à 20:49, John Covici a écrit :
> Would version 81.0.4033.2 work correctly and do I need any command
> line options?
>
> On Mon, 27 Jan 2020 12:40:21 -0500,
> Didier Spaier via orca-list wrote:
> > Hello Marko,
> >
> > you need the latest Chrome for developers:
> > https://www.google.com/chrome/dev/?platform=linux
> > and a fairly recent Orca, preferably 3.35.3 recently released
> > if not pulled from git mainline on GitHub or git master
> > on GitLab.
> >
> > Best regards,
> >
> > Didier 
> >
> > Le 27/01/20 à 18:02, Marko Marjanović via orca-list a écrit :
> > > Hello all,
> > > > From the messages on this list, I realized that many of you use Google
> > > Chrome on Ubuntu. I installed it, and it reads menus and the address
> > > edit field, but when there are links Orca behaves as if 
> > > thehttps://www.google.com/chrome/dev/?platform=linuxveru
> > > application were totaly inaccessible.
> > > I also want to emfasize that it is the original Google Chrome, not Chromium.
> > > Thank you all for your answer!