This issue came up as I was testing the PR for #1439. Everything was working beautifully in the PR sandbox, but only if you are an experienced Drupal/Backdrop user, and you can thus anticipate certain quirks we have all gotten used to over the years...
After having clicked the "Browse available tokens" link and browsed through the tokens, when you click on a token to be used, you get this error/prompt:

I realize that in theory, the token browser can be used in any field in the same page (although it does not necessarily mean that the token set specified in a "Browse available tokens" link for one field can be used in other fields), but it is annoying to have clicked a link under a specific field, and then have this error message telling you to select a field.
If the field had focus prior to the token browser dialog being opened, then any token clicked on the dialog gets properly inserted into that field, without any error/prompt; but if the focus was elsewhere before clicking the link (such as the "enable" checkboxes in this case, which show/hide the image alt/title fields using #states), then you get this UX WTF.
Can we have it so that theme_token_tree_link() accepts a field ID as a parameter, so that once the "Browse available tokens" link is clicked, there's some JS triggered, which sets the focus to that field before opening the token browser?
Recent comments
If there is time, carried over from last week as we didn't have time to look at it then, I would welcome feedback on the approach I've taken to: [A11Y] Update aria role on...
July 16th, 2026 - Weekly Meetings
If there's some time left after discussing code signing (yay!)... 1. Friendly reminder: usage stats are still broken Didn't data get fetched at all (broken parser) or is it a display...
July 16th, 2026 - Weekly Meetings
Sorry - it is the field_group module. However, last night I switched off proxying to the site and proved to Cloudflare Support that it was NOT a Backdrop issue. After a thorough...
Cloudflare specific advice needed [SOLVED]