Hey team, Facing a bit of an odd issue where select ‘values’ are not being shown. In this example, we’re only using <s-select value="val"> - and not using the selected or defaultSelected props on the <s-option>. But, we’ve replicated using those properties also. It’s also worth noting that this in…

Hey folks - the August 31 Polaris CDN 1.1 release candidate includes a Select fix for “an empty value showing before the options parse”: Polaris CDN 1.1 release candidate - Shopify developer changelog You can test this change by loading https://cdn.shopify.com/shopifycloud/polaris-1.1-rc.js. If you…

I’ve experienced this as well, and the issue was completely random. Sometimes it was showing the value, sometimes not. I suppose you’re working on React 19 ? React 19 and Polaris web components have ton of weird bugs, especially when using SSR.

[image] bakura10: SSR We see this specific one on both React 18 and 19, and across browsers (Chromium, Safari, Firefox). Good to hear it’s not just us, thank you!

I’m seeing the same issue with Polaris Web Components, even with a very basic setup: <s-select class="my_field" label="Label" value="{{ $value_set_from_backend }}"> <s-option value="0" @if($value_set_from_backend == 0) selected @endif>Value 0</s-option> <s-option value="1" @if($value_set_fr…

I believe we have a fix for this internally – letting it soak for a bit before pushing to the CDN

edit: I’m not able to replicate this consistently. I think I could be flicking between CDN edges - just a gut feel. Hey Anthony, just refreshed a few times and was still able to see the issue. It definitely happens less (requires 5-6 reloads) so imagine it’s intermittent but still there. [CleanSh…

Hey! I can confirm the issue is still present with Polaris Web Components. It’s actually the only BFS rejection reason I can’t realistically fix on my side, apart from switching back to regular HTML <select> elements, which is obviously far from ideal… It would really be great to get a definitive f…

Invisible <s-select value

Polaris

Anthony_Frehner April 29, 2026, 8:04pm 6

We just did a release – let me know if this is fixed or not. Thanks! April 29, 2026 Updates to the Admin Polaris Library

Topic		Replies	Views
Blank s-select element Polaris	3	71	August 24, 2026
S-select Polaris web component regression? Polaris	10	287	March 10, 2026
S-select not functioning as described Polaris	2	139	July 18, 2025
onChange not working on s-select Polaris new-gql-apis	6	269	April 30, 2026
Conditional Polaris component (s-text-field) rendered in wrong position after s-select change Polaris extensions	1	57	March 15, 2026

Invisible <s-select value

Related topics