Hi,
A regression has been introduced to the component, which no longer shows any button, making navigation impossible.
Code to reproduce:
<ui-title-bar title="Custom fields">
<button>Test</button>
</ui-title-bar>
End result:
Thanks!
Hi,
A regression has been introduced to the component, which no longer shows any button, making navigation impossible.
Code to reproduce:
<ui-title-bar title="Custom fields">
<button>Test</button>
</ui-title-bar>
End result:
Thanks!
EDIT: I found that this happens because now seems to support “primary-action” and “secondary-actions”.
It is a bit strange though. In Shopify admin, the s-page actions are at the bottom (typically at the end of the form), while now they appear in the title-bar. This makes it a bit inconsistent as the now seems to do nothing.
I believe they do appear at the bottom of the screen on mobile, and at the top on desktop. It also works in a similar way on the mobile app. I do agree that it feels a bit odd.
Yeah I’m already getting support emails about this, can you guys please fix this asap?
Great! Sorry for the inconvenience and thanks for flagging it ![]()
All back to normal ![]()
Thanks @Fio . This however caused a regression where the primary-action and secondary-actions no longer work for the component.
Hey @bakura10 I’ll take this back to the team but this is actually expected. Our guidance is to not have 2 sets of actions at the top of the page. If you find you have a lot of actions to surface there you can group your actions in the ui-title-bar with:
<ui-title-bar>
{...}
<section label="Grouped Actions">
<button>Additional Action 1</button>
<button>Additional Action 2</button>
<button>Additional Action 3</button>
</section>
</ui-title-bar>
Hope that helps ![]()
@Fio I am referring to the slot of the component:
<s-page>
<s-button slot="primary-action">Foo</s-button>
</s-page>
This no longer works since yesterday’s change.