Moderated Re: Chromium Fix for JAWS Problem Has Been Issued


Steve Nutt
 

That’s why I use Chrome. Edge is always behind with such fixes.

 

All the best


Steve

 

From: main@jfw.groups.io <main@jfw.groups.io> On Behalf Of Bill White
Sent: 07 October 2022 16:09
To: main@jfw.groups.io
Subject: Re: Chromium Fix for JAWS Problem Has Been Issued

 

Hi, Brian. Edge was updated, but even Microsoft admits that the newest update to Microsoft was not released to address the context menu activation issue.

 

Bill White

 

billwhite92701@...

 

From: main@jfw.groups.io [mailto:main@jfw.groups.io] On Behalf Of Brian Vogel
Sent: Friday, October 7, 2022 6:54 AM
To: main@jfw.groups.io
Subject: Chromium Fix for JAWS Problem Has Been Issued

 

And Chrome and Brave have definitely already integrated it yesterday, and I believe Edge has, too, as it's updating on my machine as I type.  One way to force updates on any Chromium-based browser is to look at Help, About {Insert browser name here}.  The About dialog always checks to see if any updates exist, and will download them for immediate application if they do.

For those who want the details, see:  https://chromium.googlesource.com/chromium/src/+log/106.0.5249.91..106.0.5249.103?pretty=fuller&n=1000 

The key tidbit:

AT actions API: Always expose default action at index 0.
 
Nodes are expected to know if they have a default action assigned, and
return that knowledge via HasDefaultActionVerb(). We found some cases
that, nonetheless, report false incorrectly on Windows platforms.
 
This causes serious regressions with JAWS, so we introduce a workaround
to expose the default action unconditionally.
 
(cherry picked from commit c287736e2fce23aef17a48bb2fd0bb1c240da75c)

--

Brian Virginia, USA Windows 10, 64-Bit, Version 21H2, Build 19044  

Puritanism: The haunting fear that someone, somewhere, may be happy.

    ~ H.L. Mencken, AKA The Sage of Baltimore

Join {main@jfw.groups.io to automatically receive all group messages.