Warning: Type of PR label mismatch

To merge this PR, it requires exactly 1 label indicating the type of PR. Other labels are optional and not being checked here.

• Required label: Any label starting with [Type].
• Labels found: .

Read more about Type labels in Gutenberg. Don't worry if you don't have the required permissions to add labels; the PR reviewer should be able to help with the task.

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: Vrishabhsk <vrishabhsk@git.wordpress.org>
Co-authored-by: henriqueiamarino <iamarinoh@git.wordpress.org>
Co-authored-by: carolinan <poena@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

Hey @Vrishabhsk, great work on this! The inline layout and tag style additions are solid improvements. It addresses a pain point and gives the designers the chance to avoid custom CSS to achieve the patterns. It's exactly what I required at the PR #75127.

One suggestion worth considering: your delimiter SelectControl with fixed options (Comma, Dot, Pipe, Slash) is a step forward, but it might be a bit rigid compared to what we already support today. Under the Advanced tab, the Categories element already accepts any character(s) in Advanced > Separator. So, by restricting it to four options, we’d move toward a more constrained experience.

What if the dropdown included a Custom option as the last choice, similar to how the Date block handles custom formats? That way, you get the discoverability and UX clarity of predefined options, while still giving power users the flexibility they’re used to. It would also keep things more coherent with the broader WP design system.

Otherwise, the implementation looks clean to me, a theme designer. We’ll need more experienced eyes after the fixes. Let me know, and I'll get someone to help us.

Hi @henriqueiamarino 👋 Appreciate the review and the design perspective!

• I've added the "Custom" option you mentioned. Now when users select it, they get a text input where they can enter whatever delimiter they want - just like the Date block handles custom formats.
• This keeps the nice UX of having discoverable presets (Comma, Dot, Pipe, Slash) for most users, while still giving power users the flexibility they're used to from the Advanced > Separator setting.

Thanks for the iteration, @Vrishabhsk. I’ll need a review from @scruffian, as the feature is good to go from a design perspective.

Hi
I am for adding style options, but there are a few things I would like us to reconsider.

I don't think that a "tag style" is something universal? Themes style tags in many different ways. What I mean is, will users immediately understand what selecting the "tag style" does?
Similarly, I think the CSS class name is too generic and not explanatory?

When the dropdown option is selected, all the tag style does is move the label to the right? And only in the editor, not the front? I personally don't find that intuitive, that the style is always available, but only applies to some options.

I'm not sure this style option lets us do what we really want?
It doesn't let us adjust spacing, add a separate background, text or link color or border styles for the items. We can still only add a background to the whole block, so when the border is added around the items, it can look pretty bad.
Because these tags are not "inner blocks".

Secondly, I am unsure about using the term "Inline" as a visible user-facing label. I could not find any other blocks that uses this label, correct me if I missed any.
Perhaps it could be "Horizontal" ?

....
Could we remove the block style variation for now and only add the options that alter the markup?