Skip to content

Add-on Store: Add-ons that were disabled due to incompatibility with NVDA are filtered to enabled #15416

Description

@cary-rowen

Steps to reproduce:

  1. Upgrade from NVDA-2023.2 to Alpha version (2024.1).
  2. Some add-ons are automatically disabled due to compatibility.
  3. Open the add-on store,
  4. Select the "Enabled" option in the "Enabled/disabled" combo box.
  5. Select any add-on, override compatibility and enable it, then manually disable the add-on again.

Actual behavior:

Step (4): Those add-ons that are automatically disabled due to incompatibility appear in the add-on list.
Step (5): As expected, that is: it can be correctly filtered as enabled or disabled.

Expected behavior:

These add-ons are actually disabled and should not be shown in the list unless the user selects "Disabled"or "All" in the "Enabled/disabled" combo box.

NVDA logs, crash dumps and other attachments:

System configuration

NVDA installed/portable/running from source:

Installed

NVDA version:

alpha-29134

Windows version:

Windows 10 22H2 (AMD64) build 19045.3393

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

None

Other information about your system:

None

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.

No

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

Already explained.

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

Yes

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    feature/addon-storeFeatures / behavior of the add-on Storep5https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#prioritytriagedHas been triaged, issue is waiting for implementation.

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions