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

User Guide has extra column in table in section 5.3 (Since 2022.1) #13821

Closed
Qchristensen opened this issue Jun 21, 2022 · 0 comments · Fixed by #13824
Closed

User Guide has extra column in table in section 5.3 (Since 2022.1) #13821

Qchristensen opened this issue Jun 21, 2022 · 0 comments · Fixed by #13824
Milestone

Comments

@Qchristensen
Copy link
Member

Steps to reproduce:

Open the user guide to section 5.3: https://www.nvaccess.org/files/nvda/documentation/userGuide.html#SystemCaret
Navigate down to the table (press t).

Actual behavior:

The table contains 8 rows and 5 columns. The columns are Name, desktop key, laptop key, description and a blank column.

In the "Report Caret location" row, there is a desktop key, laptop key, then "none" (presumably intended to be the touch navigation key?) then the description in column 5.

Expected behavior:

Remove "None" and the extra column.

System configuration

NVDA installed/portable/running from source:

NVDA version:

Tested with NVDA 2021.3.5, 2022.1 and 2022.2beta2. Issue present in 2022.1 and 2022.2beta2.

Windows version:

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?

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?

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

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 a pull request may close this issue.

2 participants