Re: google chrome version 81
|
Jason White
If I open a PDF file in Chrome 81, NVDA describes it as an "embedded object", then fails to read it. JAWS does the same, so I assume something changed in Chrome. On the other hand, VoiceOver for Mac with Chrome 81 reads PDF documents as well as ever.
toggle quoted messageShow quoted text
Is this a change that NVDA and other screen readers will need to adapt to, or is it a Chrome bug? Can others reproduce it? Note that I'm not using an external PDF reader; this is entirely with the PDF processor included in Chrome. I can of course use Adobe Reader dC instead, although Chrome was until recently giving me better results on a range of PDF files. On 4/8/20, 14:27, "Shaun Everiss" <nvda@nvda.groups.io on behalf of sm.everiss@...> wrote: well thats good to know.
On 8/04/2020 9:59 pm, Ralf Kefferpuetz wrote:
> Google Chrome 81 was released today... > > -----Original Message----- > From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Shaun Everiss > Sent: Donnerstag, 19. März 2020 01:09 > To: nvda@nvda.groups.io > Subject: Re: [nvda] google chrome version 81 > > A lot of stuff is delayed. > > Bar skype and a few codec updates nothing has been released due to this damn virus. > > Usually by now I have at least a couple releases of my display drivers for the month but nothing. > > > > On 19/03/2020 12:22 pm, Don H wrote: >> Has the release of google chrome version 81 been delayed? >> >> >> >> >> . > > > > > > > .
|
|
|