Markup appears by revision settings when translations turned on

This issue is being reviewed by the kind folks in Slack, #needs-review-queue-initiative. We are working to keep the size of Needs Review queue [2700+ issues] to around 400 (1 month or less), following Review a patch or merge request → as a guide.

Tried replicating on Drupal 10.1 with Umani install and I do not see the markup

If still valid please provide testing steps.

It does seem like it's way too aggressive. We have this unescaped HTML <span class="translation-entity-all-languages"> appearing at the end of many buttons and other form elements of a multilingual site.

For example, even something as simple as a link inside a container gets it added. The fix is to add '#multilingual' => TRUE to the container or the element. But the patch #5 will also fix it, and makes sense - what Drupal core is currently doing is incorrect because it is appending some HTML to a string that gets escaped.

Another place it will appear is in the error message for a required field - even if the field itself displays correctly, the title (with suffix) gets escaped in the error message about the required field.

The best thing might be to remove the spans, because the #title of an element is used as a string in so many places.

Decided to spin off a new issue. 🐛 HTML (all languages) appearing in error messages of multilingual sites Active

I also could not reproduce the problem stated in the issue summary. And there is a separate issue for a problem with fields. so, closing this one.