Extra parameters for suppressing the header ("Babel user information"), footer ("Users by language") and the border of the box would be nice, too, by the way.

(In reply to Waldir from comment #1)

Extra parameters for suppressing the header ("Babel user information"),
footer ("Users by language") and the border of the box would be nice, too,
by the way.

That's bug 31309.

Change 332332 had a related patch set uploaded (by Georggi199):
Fixed 2 issues with Babel boxes and categorisation of language codes

https://gerrit.wikimedia.org/r/332332

In the interim, you can achieve most layouts through applying CSS styles to a wrapping <div>.

Example of horizontal alignment:

<div style="display: flex;">
  {{#babel:plain=1|en|fr|es}}
</div>

Change 332332 abandoned by Nikerabbit:

[mediawiki/extensions/Babel@master] Fixed 2 issues with Babel boxes and categorisation of language codes

Reason:

Old, stale patch

https://gerrit.wikimedia.org/r/332332

Change 884518 had a related patch set uploaded (by Pppery; author: Pppery):

[mediawiki/extensions/Babel@master] Add |float= parameter to babel box

https://gerrit.wikimedia.org/r/884518

It was mentioned above that this can be handled by a wrapping babel in a div. What benefit is there to support this in the Babel itself?

In T66164#8571830, @Nikerabbit wrote:

It was mentioned above that this can be handled by a wrapping babel in a div. What benefit is there to support this in the Babel itself?

It was always in these templates before the switch to extension happened. This is such a commonly used construct that forcing the user to use a hack seems wrong to me.

I assume the template uses need to be manually migrated anyway, so why not migrate to more flexible solution that doesn't increase code complexity? It's not a hack, it was used for table of contents too.

It shouldn't be manual, it should be semi-automatic: T228598. Moreover, all userboxes in almost all projects have a align setting. Babel creates userboxes. And the problem with the lack of such a setting for Babel userboxes at one time gave me problems.

It is bad practice to create a UI element without the settings used in exactly the same UI elements.

As the patch author, I'm neutral in this dispute, and filed the patch primarily just because the bug existed, not because I particularly cared for the feature.

Change 884518 abandoned by Pppery:

[mediawiki/extensions/Babel@master] Add |float= parameter to babel box

Reason:

If adding support for this parameter correctly is going to be that complicated, then I'm starting to agree with Nikerabbit over on the Phabricator task that it's not worth doing.

https://gerrit.wikimedia.org/r/884518