Warnings when using s-table

[nunof]

Hey,

I’m getting a couple of warnings when using s-table.

The code structure looks correct:

<s-section padding="none">
  <s-table>
    <s-table-header-row>
      <s-table-header listSlot="primary">Name</s-table-header>
      <s-table-header>Email</s-table-header>
      <s-table-header format="numeric">Orders placed</s-table-header>
      <s-table-header>Phone</s-table-header>
    </s-table-header-row>
    <s-table-body>
      <s-table-row>
        <s-table-cell>John Smith</s-table-cell>
        <s-table-cell>john@example.com</s-table-cell>
        <s-table-cell>23</s-table-cell>
        <s-table-cell>123-456-7890</s-table-cell>
      </s-table-row>
      <s-table-row>
        <s-table-cell>Jane Johnson</s-table-cell>
        <s-table-cell>jane@example.com</s-table-cell>
        <s-table-cell>15</s-table-cell>
        <s-table-cell>234-567-8901</s-table-cell>
      </s-table-row>
      <s-table-row>
        <s-table-cell>Brandon Williams</s-table-cell>
        <s-table-cell>brandon@example.com</s-table-cell>
        <s-table-cell>42</s-table-cell>
        <s-table-cell>345-678-9012</s-table-cell>
      </s-table-row>
    </s-table-body>
  </s-table>
</s-section>

Is this a known issue or am I missing something obvious?

[bkspace]

I see the same warning, even though the structure is definitely correct as described

[mGaurav]

+1
Getting the same warnings.

[nunof]

This issue appears to be more problematic than just the warnings.

On Friday, we deployed a change to start using s-table in a core page. That change caused a huge spike in our FCP and LCP over the weekend.

It’s not clear whether the cause is the warnings related to s-table, or the component itself, but using s-table caused a significant render-blocking delay in our app.

After reverting that change, everything is back to normal:

[Anthony_Frehner]

Yeah our warnings are a little messed up at the moment; it’s on our backlog to fix them for these situations. Thanks for your patience.