#Needs subsystem maintainer review

I err on the side of not adding new settings for things unless they're deemed necessary. This feels like an edge case borne out of personal preference, not out of necessity. Thus, I'd rather see this being solved in contrib or with custom alteration. And in 5.5 years this hasn't gotten any other support aside from a reroll. So I'm going to close this as a "won't fix." If anyone feels strongly that this should be added to Core, then please feel free to re-open the ticket with arguments about why this should be implemented.

Committed e1e9732 and pushed to 11.x. Thanks!

nod_ → closed merge request !12749

The Needs Review Queue Bot → tested this issue. It fails the Drupal core commit checks. Therefore, this issue status is now "Needs work".

This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.

Consult the Drupal Contributor Guide → to find step-by-step guides for working with issues.

My previous concern about this being quite long for a theme description remains. I don't know that it's the place of the theme info file to provide links to the theming documentation? I think we could drop the last bit with the link. The updated proposal could also get a quick usability review at the weekly usability meeting. To that end, a screenshot of the description in context alongside other themes' descriptions would be helpful.

Also, this still has not had subsystem maintainer feedback. However, given that the maintainer for this subsystem was out for the past eight weeks and is currently discussing their maintainership, we can escalate this to the FEFMs.

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

I think this description makes sense, looks good to me.