Skip to content

Use blockAction.when decorator to have a message reported in secure mode when trying to open the symbol dialog#13539

Merged
michaelDCurran merged 1 commit into
nvaccess:masterfrom
CyrilleB79:useBlockAction
Mar 27, 2022
Merged

Use blockAction.when decorator to have a message reported in secure mode when trying to open the symbol dialog#13539
michaelDCurran merged 1 commit into
nvaccess:masterfrom
CyrilleB79:useBlockAction

Conversation

@CyrilleB79

Copy link
Copy Markdown
Contributor

Link to issue number:

Fix-up of #13535
Follow-up of #13500

Summary of the issue:

In #13500 a decorator has been introduced to speak a message when an action is unavailable in secure mode.
In parallel an NVDA 2021.3.5 patch release has been produced; this release contains a fix preventing to open the symbol dialog in secure mode. The 2021.3.5 (rc) branch has then been merged into master to get this fix in master.
This led to the fact that no message was reported when trying to use a script to open the symbol dialog in secure mode.

Description of how this pull request fixes the issue:

Added the blockAction.when decorator where it was missing.

Testing strategy:

  • In input gesture dialog configure a gesture to open the symbol dialog and press OK.
  • Restart NVDA with the -s parameter and execute the newly configured gesture.
    Check that the dialog does not open and that a message reports that the action is unavailable in secure screen.
    • Restart NVDA without the -s parameter and execute the newly configured gesture.
      Check that the symbol dialog opens.

Known issues with pull request:

None

Change log entries:

Not needed: fixing an issue not yet released.

Code Review Checklist:

  • Pull Request description:
    • description is up to date
    • change log entries
  • Testing:
    • Unit tests
    • System (end to end) tests
    • Manual testing
  • API is compatible with existing add-ons.
  • Documentation:
    • User Documentation
    • Developer / Technical Documentation
    • Context sensitive help for GUI changes
  • UX of all users considered:
    • Speech
    • Braille
    • Low Vision
    • Different web browsers
    • Localization in other languages / culture than English

@CyrilleB79 CyrilleB79 marked this pull request as ready for review March 25, 2022 10:16
@CyrilleB79 CyrilleB79 requested a review from a team as a code owner March 25, 2022 10:16
@CyrilleB79 CyrilleB79 requested a review from seanbudd March 25, 2022 10:16
@michaelDCurran michaelDCurran merged commit f4939b2 into nvaccess:master Mar 27, 2022
@nvaccessAuto nvaccessAuto added this to the 2022.2 milestone Mar 27, 2022
seanbudd added a commit that referenced this pull request Mar 28, 2022
Summary of the issue:
Certain mainFrame commands `gui.mainFrame.ExampleCommand` are only exposed via the NVDA menu not in secure mode.
In the future, input gestures might be created for these commands, exposing them in secure mode.

Additionally, the log viewer is disable in secure mode, so script_navigatorObject_devInfo should be blocked, as it is misleading. The logs should not be accessible when running in secure mode.
Debug logging in secure screens can be configured with the serviceDebug parameter.

Description of how this pull request fixes the issue:
Adds secure mode decorators to commands that are currently inaccessible in secure mode.

Testing strategy:
The decorator has been tested in #13539 and other PRs.
Other than script_navigatorObject_devInfo, these messages should be currently inaccessible to the user.
@CyrilleB79 CyrilleB79 deleted the useBlockAction branch March 29, 2022 11:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants