[Urgent] Buttons no longer appearing in modals

Merchants are reporting that buttons are no longer appearing in modals and I can confirm:

This is how it should render:

I stripped down the modal to the following for testing:

<s-modal id="line-discount-modal">

    <s-button
        slot="primary-action"
        variant="primary">
        Apply
    </s-button>
    
</s-modal>

It only works when the page with the modal is refreshed, if the merchants goes to a different page (ajax/xhr based routing) and tries again, the issue is back and the buttons won’t appear.

It seems that:

According to the docs, these should be the same but the file content for both versions is different

Hey Philo, we’re taking a look into the issue. In the meantime you can pin to polaris-1.0.js to unblock merchants.

@Philo are you able to provide more details on the framework you’re using, or how you’re populating the modal? I’m not able to reproduce the issue. Any information you can provide that will help us narrow down would be helpful.

Thanks @David-Shopify

I’m using Laravel + Livewire’s wire:navigate feature, similar like Turbolinks. Any idea why polaris.js and polaris-1.0.js are not the same though?

Thanks for that, we were in process of promoting the 1.1 into the stable channels. I’m going to take a look at reproducing the issue. This didn’t come up during the release candidate soak period we had.

Interestingly (and possibly related), anybody who is getting the new Shopify Admin UI and seeing modals inside of apps still running Polaris React are getting modals with really large padding in the footer/button section:

We haven’t adopted the Polaris Web Components yet, but our React components change on this new UI.

@marcbaumbach that’s a separate issue, taking a look at it but it’s not related.

@Philo we have deployed an update to https://cdn.shopify.com/shopifycloud/polaris-1.1-rc.js can you verify that this has resolved the issue?

@David-Shopify I can confirm that the issue is resolved when using the 1.1-rc.js release :slight_smile: Thanks for the quick update.

@marcbaumbach the issue you reported should also be fixed now.

Thank you! I can confirm it’s fixed.