Very weird issue here. I lost multiple days trying to figure this out.
The s-table component sometimes doesn’t render cells that aren’t primary or labeled when viewed on mobile.
I have to rotate the phone to landscape mode and then back to portrait in order for the cells to appear properly.
It must have something to do with rendering on the mobile device initially, some styles are hiding those cells?? but then when the phone is rotated it causes the web component to recalculate the styles.
It can be very intermittent, but I find it happens more often when you have a complex table.
Hey @ozzyonfire -
Thanks for flagging this. This does look similar to another s-table mobile rendering report we’ve seen around kicker, inline, and secondary list slots not appearing on first render, then showing after a rotation forces the component to recalculate: Community issue report.
Could you share a minimal reproduction if you have one, along with the device/iOS version and whether this is happening in the Shopify mobile app, mobile Safari, or both? I’m going to connect this with the existing report on our end since the “portrait load missing cells, rotate fixes it” behaviour is a pretty strong match.
In the meantime, I’d avoid putting critical controls only in kicker, inline, or secondary on mobile if you can work around it, since those are the slots that seem most affected here.
Hope to hear from you soon!