Focus tab title instead of panel switching tabs in add-on store#15988
Conversation
I strongly agree with this proposal. I've reviewed changes and tested them, and I'd approve them if the changes.t2t file would reflect this, probably in the section corresponding to fixes, with credits to you @ABuffEr |
|
@ABuffEr really nice touch! I was always baffled by NVDA's behavior upon pressing Control+Tab in the Add-on Manager. |
Hi @nvdaes, |
You need to update 'changes.t2t`. See the Change log entry section in contributing.md |
XLTechie
left a comment
There was a problem hiding this comment.
@ABuffEr this is great, a much improved user experience for tab changing in the store.
@seanbudd @michaelDCurran Please do consider including in beta!
lukaszgo1
left a comment
There was a problem hiding this comment.
I'm fine with this, as long as we agree that this is a work around, and ideally list of add-ons should be focused.
|
Sincerely, I'm not totally convinced about the best element to be focused. Some people may prefer to focus the box to filter add-ons. But imo this pr is crutial and should be included in NVDA 2024.1. |
I agree at least until #15947 is solved/implemented; then, focusing on add-on list sounds more reasonable, and coherent with what happens e.g. in symbols dialog. |
I think this should be discussed in a different thread, since the fact that we use lists at the end doesn't mean that we want to start focusing lists in NVDA dialogs, even if this has been done during long time. |
|
Looking at this pr and associated issue, I wonder why the MultiCategorySettingsDialog approach wasn't chosen for the add-ons manager. That has custom logic for ctrl+tab I believe. |
|
I have not tested this PR. But from the description, I fully support its inclusion in beta branch (cc @seanbudd, @michaelDCurran). The discussion on the best place where the focus should land can still remain open after merging this PR. |
| - When reinstalling an incompatible add-on it is no longer forcefully disabled. (#15584, @lukaszgo1) | ||
| - Disabled and incompatible add-ons can now be updated. (#15568, #15029) | ||
| - NVDA now recovers and displays an error in a case where an add-on fails to download correctly. (#15796) | ||
| - When pressing ctrl+tab, focus properly moves to the new current tab title. (#14986, @ABuffEr) |
There was a problem hiding this comment.
this PR is targeting master and should go into 2024.2. Please move the change log to 2024.2.
There was a problem hiding this comment.
My mistake, looking now at branches available I suppose to have to do a PR targeting beta; if you'll accept it I close this and open another PR. I'll move changelog line otherwise, but 2024.1 would be preferable.
There was a problem hiding this comment.
2024.1 is already deep into beta stage - it is too late for risky changes of behaviour - particularly this case where it is generally agreed that it might not be the final behaviour. I believe the behaviour included in this PR was part of the original add-on store PR (if not, it was something similar) which was reverted to the current behaviour based on feedback.
There was a problem hiding this comment.
I strongly doubt that there was a feedback against this feature, I'm quite sure it's an accessibility issue of that wx control from a long time ago (I mean, at least since we changed settings structure years and years ago).
Anyway, ok, I disagree but will change release target in changelog with next commit. Move it as needed if discussion proceeds.
There was a problem hiding this comment.
For reference, the prototype set focus to the add-on list view, this was later reverted due to feedback and the comment/issue was created to find a new solution.
|
Hi @seanbudd This is a useful improvement, I receive this feedback frequently in the Chinese community, and I agree that it should be targeted for 2024.1.
|
Co-authored-by: Sean Budd <seanbudd123@gmail.com>
Co-authored-by: Sean Budd <seanbudd123@gmail.com>
…cess#15988) See discussion in nvaccess#14986 Summary of the issue: Switching tabs in add-on store with ctrl+tab announces "tab control panel", and moves the focus in a strange position. Description of user facing changes Users will be positioned on tab list, over the new current tab, that will be read by NVDA. Description of development approach Simply SetFocus on addonListTabs (wx.Notebook) if it's not already here, at the end of page change event handler.
…cess#15988) See discussion in nvaccess#14986 Summary of the issue: Switching tabs in add-on store with ctrl+tab announces "tab control panel", and moves the focus in a strange position. Description of user facing changes Users will be positioned on tab list, over the new current tab, that will be read by NVDA. Description of development approach Simply SetFocus on addonListTabs (wx.Notebook) if it's not already here, at the end of page change event handler.
…cess#15988) See discussion in nvaccess#14986 Summary of the issue: Switching tabs in add-on store with ctrl+tab announces "tab control panel", and moves the focus in a strange position. Description of user facing changes Users will be positioned on tab list, over the new current tab, that will be read by NVDA. Description of development approach Simply SetFocus on addonListTabs (wx.Notebook) if it's not already here, at the end of page change event handler.
Link to issue number:
See discussion in #14986
Summary of the issue:
Switching tabs in add-on store with ctrl+tab announces "tab control panel", and moves the focus in a strange position.
Description of user facing changes
Users will be positioned on tab list, over the new current tab, that will be read by NVDA.
Description of development approach
Simply SetFocus on addonListTabs (wx.Notebook) if it's not already here, at the end of page change event handler.
Testing strategy:
Manual, with steps in #14986.
Known issues with pull request:
It's a partial fix, as discussed in #14986, because it doesn't move focus to a panel element like the channel filter or the add-on list, that seems unreasonably complex to reach. But it's certainly better than nothing/current situation.
Being a small but very perceptible change, I suggest to integrate into 2024.1, and only later to work on another better solution.
Code Review Checklist: