Field buttons (data-responsive) collapse to icon-only when their container is narrower than 30rem. In blueprints that use columns, a 1/3 sidebar column often sits below that threshold on typical desktop widths while the 2/3 main column sits above it. As a result, the same kind of button (“Add”, “Select”, “Upload”) can show its label in one field and only an icon in another, on the same screen. Since the varying factor (container width) isn’t visible to editors, they may perceive this as inconsistency rather than as responsive behavior.
Would it be worth making the collapse threshold configurable (a panel option or a CSS custom property), or perhaps lowering the default a bit so labels survive in typical sidebar columns? I currently work around it in a custom panel CSS (restoring the :root defaults inside the 30rem container query and re-collapsing at 16rem), which works fine for me, but it relies on internal selectors.
A small related observation: the structure field offers the same add action three times (labelled header button, “Add” in the options dropdown, and an icon-only “+” below the table), while other field types only have the header buttons. This is a bit confusing and also the help text has to be located lower than perhaps necesary. Maybe the footer button could be optional. This may well be intentional, though, so feel free to disregard.
(I am on Kirby 5.5.1.)