Re: [orca-list] Orca master, Chrome unstable gmail problems
- From: Andy Borka <sonfire11 gmail com>
- To: Orca List <orca-list gnome org>
- Subject: Re: [orca-list] Orca master, Chrome unstable gmail problems
- Date: Fri, 13 Mar 2020 14:53:58 -0400
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.
- Start Orca master
- Put ACCESSIBILITY_ENABLED=1 in your environment.
Start Chrome unstable (latest update) with above flags.
Close that instance of Chrome.
Start Chrome without the accessibility flags.
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.
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]