Re: [orca-list] Orca master, Chrome unstable gmail problems

[Joanmarie Diggs <jdiggs igalia com>]

As I mentioned to Alex, you still need --enable-caret-browsing for text 
selection. That is not an accessibility flag. The only flag that has (so 
far) been eliminated is --force-renderer-accessibility.

On 3/13/20 14:53, Andy Borka via orca-list wrote:
> Hi,
>
> Using Google Chrome unstable with flags generally works. This is what I 
> have in my setup:
>
> in .profile:
> ACCESSIBILITY_ENABLED=1
> export ACCESSIBILITY_ENABLED
>
> in google-chrome.sh:
>
> google-chrome-unstable --force-renderer-accessible --enable-caret-browsing
>
> It worked fine until chrome-unstable had an update yesterday. When I 
> tried to run chrome-unstable without the above flags, Orca was able to 
> access the contents of the pages I visited. However, accessing it for 
> the first time left Orca in a state of limbo. It has now affected using 
> Chrome with the above flags.
>
>  1. Start Orca master
>  2. Put ACCESSIBILITY_ENABLED=1 in your environment.
>  3.
>     Start Chrome unstable (latest update) with above flags.
>
>  4.
>     Try to access the internet such as www.google.com
>     <http://www.google.com>
>  5.
>     Close that instance of Chrome.
>  6.
>     Start Chrome without the accessibility flags.
>  7.
>     Try to access www.google.com <http://www.google.com>
>
> Actual results: Orca is acting unreliably and has experienced extreme 
> lag. In fact, the normal way of accessing gmail doesn't work.
> Expected results: Both instances of Chrome should be accessible. At very 
> least, the instance with flags should work as before.
>
> Unless this is a regression in Orca, but this didn't start until Chrome 
> updated.
>
> Orca master, Chrome unstable, Ubuntu 20.04.
>
>
> On Fri, Mar 13, 2020 at 2:07 PM Joanmarie Diggs <jdiggs igalia com 
> <mailto:jdiggs igalia com>> wrote:
>
>     Alex: I'm afraid I don't understand this at all either. What is "the
>     selection to work"? Mind writing this in the form of steps to reproduce?
>
>     On 3/13/20 14:00, Alex ARNAUD via orca-list wrote:
>      > Le 13/03/2020 à 18:57, Alex ARNAUD via orca-list a écrit :
>      >> The startup issue only occurs with ACCESSIBILITY_ENABLED set to
>     1 in
>      >> the environment variable.
>      >
>      > This also prevents the selection to work.
>      >
>      > _______________________________________________
>      > orca-list mailing list
>      > orca-list gnome org <mailto:orca-list gnome org>
>      > https://mail.gnome.org/mailman/listinfo/orca-list
>     <https://mail.gnome.org/mailman/listinfo/orca-list>
>      > Orca wiki: https://wiki.gnome.org/Projects/Orca
>     <https://wiki.gnome.org/Projects/Orca>
>      > Orca documentation: https://help.gnome.org/users/orca/stable/
>     <https://help.gnome.org/users/orca/stable/>
>      > GNOME Universal Access guide:
>     https://help.gnome.org/users/gnome-help/stable/a11y.html
>     <https://help.gnome.org/users/gnome-help/stable/a11y.html>
>      >
>
>     _______________________________________________
>     orca-list mailing list
>     orca-list gnome org <mailto:orca-list gnome org>
>     https://mail.gnome.org/mailman/listinfo/orca-list
>     <https://mail.gnome.org/mailman/listinfo/orca-list>
>     Orca wiki: https://wiki.gnome.org/Projects/Orca
>     <https://wiki.gnome.org/Projects/Orca>
>     Orca documentation: https://help.gnome.org/users/orca/stable/
>     <https://help.gnome.org/users/orca/stable/>
>     GNOME Universal Access guide:
>     https://help.gnome.org/users/gnome-help/stable/a11y.html
>     <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