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.
I think this issue is a good idea. If you want to embed a form in a block, and that block occurs more than one time on the same page, then you have an ID conflict due to hardcoding the wrapper ID. I don't know of any workaround as-is.
- 🇮🇳India gauravvvv Delhi, India
Patch #62, no longer applies to 10.1.x. I have re-rolled the patch #62, for 10.1.x. Please review
There is size difference with the patch #62, as es6.js files are removed from the current patch.
- 🇺🇸United States smustgrave
Deprecation needs updating.
Also this was tagged for issue summary update 4 years ago. is #55 good enough?
Proposed solution could be cleaned up I think.
- Status changed to Closed: won't fix
10 days ago 11:48am 21 July 2025 - 🇺🇸United States fathershawn New York
We are on a path to deprecate Ajax API. New functionality is now out of scope, however the new subsystem accepts any valid CSS selector by design. See 🌱 Gradually replace Drupal's AJAX system with HTMX Active .
- 🇬🇧United Kingdom catch
Usually for issues like this that we're hoping to make irrelevant, I move them to postponed on the issue/meta that will do that. That way there's a way to come back and point people to the new way when it's done, while still discouraging work on something that's unlikely to get reviewed/committed before it's removed anyway.
Marking postponed on 🌱 Gradually replace Drupal's AJAX system with HTMX Active for now