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

[Andy Borka <sonfire11 gmail com>]

Hi,

The specific version of Chrome is 82.0.4083.0.

Further exploration with the problem gives me the following  results:

1. When Chrome first loads, the page is accessible, but not usable. I have to wait a long time before interacting with it.
2. Gmail doesn't work as fast as it once did.
3. More often than not, using the gmail inbox with focus mode on doesn't read anything.
4. live regions in gmail aren't spoken anymore. For example, conversation opened, message sent, etc.

It so happens that I am using Chrome unstable without the accessibility flags to write this reply. We shall see if it works the next time.

On Fri, Mar 13, 2020 at 2:53 PM Andy Borka <sonfire11 gmail com> 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
5. Close that instance of Chrome.
6. Start Chrome without the accessibility flags.
7. Try to access 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> 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
> 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