The Needs Review Queue Bot → tested this issue. It either no longer applies to Drupal core, or fails the Drupal core commit checks. Therefore, this issue status is now "Needs work".
Apart from a re-roll or rebase, this issue may need more work to address feedback in the issue or MR comments. To progress an issue, incorporate this feedback as part of the process of updating the issue. This helps other contributors to know what is outstanding.
Consult the Drupal Contributor Guide → to find step-by-step guides for working with issues.
- Status changed to Closed: duplicate
over 1 year ago 11:20am 28 April 2023 - 🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺
Is this even still relevant?
AFAICT it's not possible to automatically determine which element to focus after an AJAX command — it's context-dependent.
#3188938: Create AjaxCommand for focusing that does not require :tabbable selector → added an AJAX command to make it feasible to do focus handling correctly, allowing each UI to handle it correctly in their context. Closing as a duplicate of that.