Implement tab navigation#15332
Conversation
See test results for failed build of commit 21b08ab2ec |
|
Can you please add these gestures to the SingleLetterNavigation section of the user guide? |
|
All done. |
|
I'm afraid this pr is incomplete as is as it doesn't add support for UIA browse mode. Also mshtml isn't covered, thought that might be less relevant. Also, personally I'd vote for leaving the tab quicknav gestures unassigned by default, as per a similar rationale as in #9227 |
Yes, that's probably a good idea. |
|
Should unassigned gestures be documented somewhere? |
|
That's a good point. They certainly deserve their space in the browsmode section, probably just below the assigned ones.
|
seanbudd
left a comment
There was a problem hiding this comment.
Looks good, just needs user guide documentation
As far as I understand, unassigned gestures are undocumented right now, so I think it's worth creating a new PR for this. |
|
You are correct that this is the current norm, however as per #13024, it would be ideal to document these features in the user guide anyway. An unbound gesture should still be a documented feature in NVDA. If you can write some basic documentation, we can help with expanding it, grammar, spelling and sentence structure. |
|
Should these gestures be included in the Commands quick reference? |
This comment was marked as off-topic.
This comment was marked as off-topic.
|
Why did it fail? |
I don't think so, but maybe? I'd like to see this discussed on #13024. Including key commands is done automatically with the macro
Apologies, our test randomly fail due to the AppVeyor environment messing with focus. Don't worry about this issue. |
seanbudd
left a comment
There was a problem hiding this comment.
Thanks for adding documentation. This generally looks good
See test results for failed build of commit 1f55146aad |
Qchristensen
left a comment
There was a problem hiding this comment.
Slight update to the user guide change, otherwise looks good.
Link to issue number:
#15046
Summary of the issue:
The lack of the ability to quickly switch to tabs complicates navigation
Description of user facing changes
Users will be able to switch between tabs in web documents, by assigning the appropriate gesture.
Description of development approach
Testing strategy:
Manual
Known issues with pull request:
None
Change log entries:
New features
Added ability to quickly navigate through the tabs, the gestures are not set by default.
Changes
None
Bug fixes
None
For Developers
None
Code Review Checklist: