Ui Extensions: `<Grid/>` vs `<s-grid/>` regressions | 2

Extensions
,
1

Hi Shopify Team @ui-extensions !

While working on our React to Preact migration, we’ve hit roadblocks for this component.

React: Grid
Preact: s-grid

Would it be possible to address the following regressions?:

  • rows- Replaced partially by gridTemplateRows.
    • rows used to define both grid-template-rows and also grid-auto-rows in CSS. This would allow us to create grids that had rows of the same size based on the tallest row available via rows='fill'. This is no longer possible and after trying countless workarounds, it’s not possible to reliable do it dynamically.
    • If you could expose gridAutoRows (and possible gridAutoColumns too) as a prop that would solve the issue for us. Is that possible?

Checks:

  • Docs, confirm regression.
  • IDE, confirms regression.
  • Trying to implement, confirms regression.

Context:

  • @shopify/ui-extensions-react: 2025.7.3
  • vs
  • @shopify/ui-extensions: 2026.4.3

Thank you very much!

2

I did a little research on this. But this is what i found. I could be wrong tho. --this is a real gap in the current component, not something you’re missing I checked the official property reference and there’s no gridAutoRows/gridAutoColumns prop, and the old rows=‘fill’ behavior relied on setting both grid-template-rows and grid-auto-rows together, which gridTemplateRows alone can’t replicate. There’s no clean CSS workaround for it either. Your best move is filing this as a feature request directly with Shopify’s UI Extensions team (their public GitHub repo or dev feedback channel) this needs Shopify to expose the prop, not something fixable from the app side.

3

Thanks for the detailed write-up and investigation.

I checked with the team that owns the UI extensions component API and can confirm the gap: the legacy React set both grid-template-rows and grid-auto-rows, while only exposes gridTemplateRows, so there’s currently no way to reproduce rows=“fill” for implicit rows.

To answer the underlying question: the omission of gridAutoRows / gridAutoColumns was intentional, not an oversight. The s-* API deliberately started with a reduced surface area, with the expectation that properties like these would be added once a concrete need came up. Your report is that need.

The team is open to exposing these, but it has to land in the shared component API spec before it can flow through to @shopify/ui-extensions. No timeline to share yet, but the request is logged and this thread is the use case behind it.

If you can add a short snippet of the layout you’re building (and how it looked with rows=“fill”), that helps with prioritization.