- 🇨🇦Canada mgifford Ottawa, Ontario
So this is a keyboard focus issue? I'm just trying to figure out what the impact here will be and how it relates to accessibility.
- 🇳🇱Netherlands seanB Netherlands
In some cases you want to specifically set focus to an element after an AJAX request. The form API does not support this by default through the
#ajax
key, and it would be nice for DX if this would be supported.This is not specifically an accessibility problem, but it does have some relation. It would be good to confirm if we need accessibility sign off for this.
- 🇨🇦Canada mgifford Ottawa, Ontario
It would be important to verify that there are good defaults and that it will help site builders ensure that keyboard navigation follows a logical order. It sounds like this could prevent some keyboard-only accessibility errors. Would need to understand the problems users face without this.
- 🇩🇪Germany Anybody Porta Westfalica
Just a sidenote here: I just noticed that even the
'disable-refocus'
property was entirely undocumented at the "Full list of available #ajax properties" at https://www.drupal.org/docs/drupal-apis/javascript-api/ajax-forms#ajax_p... →Quite funny, but such cases of course cost users a lot of time in a Drupal, where there's are rarely other sources for attributes. So we all should keep in mind how important (especially API / developer) documentation is for the success of Drupal and DX.
@Pancho already commented that it's "(undocumented)" 2019!
- 🇫🇮Finland lauriii Finland
FWIW, there's an issue to add the missing properties to the AJAX API documentation: 🐛 Improve ajax system documentation to include advanced settings Active .
- 🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺
🐛 Focus state bug on text field AJAX calls Fixed landed. Let's get this issue summary updated to explain why
$element['#ajax']['refocus-blur']
is insufficient. Docs: https://www.drupal.org/node/3393717 → .