Inline fields in components v2

[xPaw]

These: https://discord.com/developers/docs/resources/message#embed-object-embed-field-structure

I can't think of a way to display multiple values in a row currently in the new components. Maybe we need some kind of grid/table.

[Hanashi]

I'm also a bit surprised why Discord didn't included features from embeds in the new components v2.

[EL-JAYY]

This is a much needed and asked topic of a lot of developers as far as i know.
For many use cases inlined fields / maybe even only text orientation (left / center / right) is very much needed to display information in a nice manner.
Often mobile usage is fine with this as well, as the fields wrap below each other.

[alexgillon]

Adding my support to this - maybe certain components could just have an 'inline' option?

It would definitely be handy to be able to display components side by side in some way

[xGronox]

Bump!

[realsubconsciousness]

Bump. Really needed!

[SirCastik]

Hi Discord ❤️ ! We would really appreciate having this on v2 components.

I know the biggest issue with embed "inline" property was mobile compatibility - but smart developers made it work, and bot users happily (or blissfully obliviously) lived with it for years. Right now, we need to use weird text alternatives like " | ", " / ", "--"... I even made an emoji that is just a blank square with the background color of the message (doesn't work properly across all media sizes)..

The point is that an overall good, widely uses, feature was taken away.. and we're sad about it.

Thanks in advance!

[ArnoldsK]

[advaith1]

please do not bump GitHub issues or discussions. it creates pointless notifications and does not help. comment if you actually have constructive information that wasn't posted previously, otherwise just upvote.

[davidstown]

Would be cool if they also added thumbnails

[dev-lush]

Thumbnails have been added as an "accessory" for the section component ("type": 9)
https://discord.com/developers/docs/components/reference#section

[dev-lush]

I expected the mobile view to have an inline display for accessory buttons too

[AlmostSuspense]

i think advaith said they didn't do this because they didn't want devs to force themselves to use short labels to make accessory buttons fit inline

[dev-lush]

i think advaith said they didn't do this because they didn't want devs to force themselves to use short labels to make accessory buttons fit inline

Wouldn't it better to have some sort of conditionals based on characters present in the text display or the button's label to make it inline or not in the client's view?

[AlmostSuspense]

that encourages shorter labels

[uBreeze]

I understand the concerns with mobile compatibility but I would like to bring up the argument that there is a strong use-case for some implementation of columns/tables/inline fields in Components V2, even if mobile renders it vertically.

I help maintain an RPG information bot, and one of the embeds we used needs to display 16 separate stats, various character information, and related metadata. With the standard embed, this worked very well: desktop users saw a compact horizontal layout, and mobile users saw a stacked vertical layout. The mobile version didn't look the same, and was longer, but was still perfectly legible. This design was used across hundreds of servers and pushed to several hundred thousand users for several years without meaningful pushback and pretty solid reception. I am sure users were occasionally inconvenienced by the embed's height, but I think that is preferable to losing the structure entirely.

Components V2 is a clear improvement overall, and we would love to implement some of the features, as interactive components are fantastic and have the potential to dramatically improve our application, but losing any equivalent to inline fields makes it extremely challenging for any realistic implementation. The current alternatives mean faking columns with separators (as @SirCastik mentioned, and looks absolutely terrible), generating images, or redesigning around a limitation that the "downgraded" version handled naturally. It feels almost redundant to restrict developers because of potential inconveniences and hurt these kinds of usecases universally, rather than allow developers to use the feature freely, and handle the consequences of any UX issues themselves.

A few compromises might be a column/grid system, such as the one suggested in #7558 or some kind of collapsible component so that unwanted information is less of an issue for smaller screens. But I think the simplest solution really is just to do the exact same thing you already had for years; allow us to design our embeds with inline fields.

[LemonCubeDev]

Upvote! I really like how you can put all component types inside a container, making it nicer, but I have to use old embeds when I want inline fields. I would appreciate being able to have inline text just like how you can have text + thumbnail or text + button

[RayKoopa]

I just wanted to improve my embeds with componentsV2, but it's not going to happen as I have semi-tabular data spanned over 3 embed fields.

Dearly needed or componentsV2 will eat dust on my side.