Re: [orca-list] Chrome Locking Up
- From: Joanmarie Diggs <jdiggs igalia com>
- To: Nimer Jaber <nimerjaber1 gmail com>
- Cc: orca-list <orca-list gnome org>
- Subject: Re: [orca-list] Chrome Locking Up
- Date: Mon, 11 Jul 2022 11:33:57 +0200
Something else to try: Do not use --force-renderer-accessibility, but disable chrome://flags/#enable-auto-disable-accessibility and restart chrome.
--joanie
On Sat, 2022-07-09 at 17:29 -0700, Nimer Jaber wrote:
Hello,
Running Chrome with force-renderer-accessibility does, indeed, rectify this problem. For the longest time, this flag wasn't needed, so I didn't think of running Chrome with it...
Does it make a difference if you launch Chrome with --force-renderer-accessibility?
On Fri, 2022-07-08 at 17:26 -0700, Nimer Jaber via orca-list wrote:
Unfortunately, nothing shows up in the generated debug.out. Wondering if there is some sort of logging in Chrome to try to pin this down... So it seems that arrow keys and navigation commands still work, but tab does not work, neither do keyboard shortcuts used by web apps, such as j and k in Gmail or Twitter.
On 8/7/22 19:41, Nimer Jaber via orca-list wrote:
> Apologies, I'm writing this without speech, as the Chrome issue where
> Orca stops speaking seems to happen now in Chrome stable as well, with
> both exhibiting the same behavior. Orca works for a couple of minutes,
> but then stops reading any of the web page. Again, is anyane
> experiencing this?
I'm not experiencing this, but I suggest you turn on debugging in Orca,
and look for relevant error messages in the debug log.
_______________________________________________
orca-list mailing list
_______________________________________________
orca-list mailing list
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]
