Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NVDA Does Not Always Refresh the Screen With Dynamic Content in Chrome #10801

Closed
frastlin opened this issue Feb 19, 2020 · 6 comments
Closed

NVDA Does Not Always Refresh the Screen With Dynamic Content in Chrome #10801

frastlin opened this issue Feb 19, 2020 · 6 comments

Comments

@frastlin
Copy link

@frastlin frastlin commented Feb 19, 2020

Steps to reproduce:

  1. With Chrome running, visit:
    https://lenovo.com/
  2. Click on "Laptops"

Actual behavior:

Nothing happens

Expected behavior:

NVDA act as if a new page has loaded.

System configuration

NVDA installed/portable/running from source:

Installed

NVDA version:

2019.3

Windows version:

10 64 bit

Name and version of other software in use when reproducing the issue:

Chrome Version 80.0.3987.106 (Official Build) (64-bit)

Other questions

Does the issue still occur after restarting your PC?

Yes

Have you tried any other versions of NVDA? If so, please report their behaviors.

This only started happening after I updated to NVDA 2019.3 from 2019.2.1. NVDA 2019.2.1 worked just fine.
I have not tested on 2019.2.1 since I updated.

Other Comments

To get the page to load I need to press NVDA F5, then something will happen and when I hit up and down arrow keys, I hear "blank". If I then hit tab, I will hear the content of the new page.

@Novalis7747

This comment has been minimized.

Copy link

@Novalis7747 Novalis7747 commented Feb 21, 2020

confirmed with 2019.3.1 and latest Chrome. This also applies for other sites as well.

@Timtam

This comment has been minimized.

Copy link

@Timtam Timtam commented Feb 24, 2020

Can confirm that this behaviour started somewhere close to the 2019.3 release. I'm always running the latest alpha and I remember that it started happening close to Chrome releasing V 80, so I was under the impression that this update is the culprit here. This bug however is rather annoying on dynamically generated websites by forcing you to always press F5 to show the new website, which also resets you to the top of the page in several cases, requiring you to search where you stopped reading.

@Qchristensen

This comment has been minimized.

Copy link

@Qchristensen Qchristensen commented Feb 25, 2020

From some testing myself (news.com.au seems a "good" site to test this on - it either happens when going from the main site to an article, or when going from an article back to the main site).

This also happens with NVDA 2019.2.1, which seems to confirm it is a change in Chrome rather than NVDA. It can be tricky as Chrome updates in the background without input from the user, and when something happens around the time NVDA releases an update, it can be easy to think it's something with NVDA.

Comments on the NVDA email group suggest this issue affects Jaws as well.

@Novalis7747

This comment has been minimized.

Copy link

@Novalis7747 Novalis7747 commented Feb 25, 2020

@Qchristensen

This comment has been minimized.

Copy link

@Qchristensen Qchristensen commented Feb 25, 2020

Going on @Novalis7747 comment both confirming that this is an issue in Chrome, and further that it appears to be fixed in Chrome 81, is it worth closing this issue?

Looking at https://www.chromestatus.com/features/schedule Chrome 81 is due for Stable release on March 17

@Adriani90

This comment has been minimized.

Copy link
Collaborator

@Adriani90 Adriani90 commented Feb 26, 2020

Closing as fixed in Chrome 81 Beta. Thanks for reporting.
@Qchristensen yes this should be ok, this is consistent with what we are also doing with Firefox issues.

@Adriani90 Adriani90 closed this Feb 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
5 participants
You can’t perform that action at this time.