-
-
Notifications
You must be signed in to change notification settings - Fork 783
Addon store restart dialog is overlaping installtasks dialog #15613
Copy link
Copy link
Closed
Labels
feature/addon-storeFeatures / behavior of the add-on StoreFeatures / behavior of the add-on Storep2https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priorityhttps://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#prioritytriagedHas been triaged, issue is waiting for implementation.Has been triaged, issue is waiting for implementation.
Milestone
Metadata
Metadata
Assignees
Labels
feature/addon-storeFeatures / behavior of the add-on StoreFeatures / behavior of the add-on Storep2https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priorityhttps://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#prioritytriagedHas been triaged, issue is waiting for implementation.Has been triaged, issue is waiting for implementation.
Type
Fields
Give feedbackNo fields configured for issues without a type.
Steps to reproduce:
Make a simple addon and in installtasks.py, in method onInstall try to show some informational message.
install it from addon store as you install an addon from available addons tab, not with install external button
Actual behavior:
When pressing close button, dialog is shown but shortly is overlapped with NVDA's restart dialog
Expected behavior:
Dialog should stay alive untill it is closed.
NVDA logs, crash dumps and other attachments:
System configuration
NVDA installed/portable/running from source:
Installed
NVDA version:
Version: alpha-29601,f1c73d1d (2024.1.0.29601)
Windows version:
Windows 10 22H2 (AMD64) build 19045.3448
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.
All versions which include addon store
If NVDA add-ons are disabled, is your problem still occurring?
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?