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

A blank window appears when the user refuses to restart NVDA after an add-on installation #14304

Open
paulber19 opened this issue Oct 27, 2022 · 4 comments
Labels
blocked/needs-technical-investigation Issue is blocked. A technical investigation is required to progress the issue. p5 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority triaged Has been triaged, issue is waiting for implementation.

Comments

@paulber19
Copy link

Steps to reproduce:

Actual behavior:

  • install an add-on
  • at the end of installation, the "restart NVDA" dialog is displayed.
  • this dialog asks the user: Changes were made to add-ons. You must restart NVDA for these changes to take effect. Would you like to restart now?"
  • now press the "No" button.
    The dialog is closed and a empty window is shown and NVDA remains silent. The title of this window is "NVDA". The "escape" key don't close it.
    This empty window disappears when changing window with "alt+tab".

Expected behavior:

the dialog should close without an empty window.

NVDA logs, crash dumps and other attachments:

System configuration

NVDA installed/portable/running from source:

Installed and portable

NVDA version:

All versions

Windows version:

Windows 10

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

Other information about your system:

Other questions

Does the issue still occur after restarting your computer?

Yes

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

If NVDA add-ons are disabled, is your problem still occurring?

Yes

Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?

Yes

@michaelDCurran michaelDCurran added triaged Has been triaged, issue is waiting for implementation. p5 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority labels Nov 1, 2022
@feerrenrut
Copy link
Contributor

This can be reproduced. But will need further investigation.

@feerrenrut feerrenrut added the blocked/needs-technical-investigation Issue is blocked. A technical investigation is required to progress the issue. label Nov 1, 2022
@CyrilleB79
Copy link
Collaborator

@paulber19, is this issue still reproducible in the Add-on Store with the last beta (2024.1beta5) or the last alpha?

@lukaszgo1
Copy link
Contributor

This is still reproducible in each case where gui.messageBox is called using mainFrame as a parent window. I have investigated this briefly in the past (I believe I've posted my conclusions in some duplicate of this issue, but cannot find it). This regressed in NVDA 2021.1, where after we Updated WX, our mainFrame gets focus when closing modal message boxes. This is pretty annoying, since if user presses Alt+F4 at this point NVDA is closed, as our main frame receives a close event.

@paulber19
Copy link
Author

paulber19 commented Jan 23, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocked/needs-technical-investigation Issue is blocked. A technical investigation is required to progress the issue. p5 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority triaged Has been triaged, issue is waiting for implementation.
Projects
None yet
Development

No branches or pull requests

5 participants