Skip to content

Create virtual buffer for Chrome content even if STATE_SYSTEM_BUSY is present #13306

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

Closed
joanmarie opened this issue Feb 4, 2022 · 0 comments · Fixed by #13851
Closed

Create virtual buffer for Chrome content even if STATE_SYSTEM_BUSY is present #13306

joanmarie opened this issue Feb 4, 2022 · 0 comments · Fixed by #13851
Assignees
Labels
app/chrome app/edge/anaheim MS browser, chromium based, replaces Spartan in 2019 by Anaheim. NVDA access via IA2. GoogleWork

Comments

@joanmarie
Copy link

As described in this Chromium bug, it was pointed out to me that adding the busy state on documents during load could by side effect cause NVDA to not create a virtual buffer until loading was complete. Therefore, my Chromium change adds the busy state for all platforms but then strips it out for IA2 so as not to introduce any problems for NVDA users.

Since a page in the process of loading is arguably busy, it would be great if NVDA did not block virtual buffer creation on the presence of this state so that we can remove the special handling for IA2.

Thanks in advance for considering this!

@feerrenrut feerrenrut added GoogleWork app/chrome app/edge/anaheim MS browser, chromium based, replaces Spartan in 2019 by Anaheim. NVDA access via IA2. labels Jun 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
app/chrome app/edge/anaheim MS browser, chromium based, replaces Spartan in 2019 by Anaheim. NVDA access via IA2. GoogleWork
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants