Sticky table header does not work if a table placed in a closed 'details' element

Thank you for reporting,

As a bug will need test coverage to show the problem.

Also recommended to use MRs now as patches are no longer auto ran and will be phased out.

Created MR for the patch.

The Needs Review Queue Bot → tested this issue.

While you are making the above changes, we recommend that you convert this patch to a merge request → . Merge requests are preferred over patches. Be sure to hide the old patch files as well. (Converting an issue to a merge request without other contributions to the issue will not receive credit.)

Perhaps the solution can be more targeted and the sticky recalculated on the details toggle event instead of the current approach that uses the more-often-occuring scroll event.

It's also worth pointing out that this will likely no longer be an issue once this issue lands: 📌 Make drupal.tableheader only use CSS for sticky table headers Needs review

However, that would only benefit 11.x, and it would be nice to get this bug addressed for Drupal 10 so this could still be worth doing.

The current MR works only if we change table.sticky-enabled to table.position-sticky in this

function tableHeaderInitHandler(e) {
    once('tableheader', $(e.data.context).find('table.sticky-enabled')).forEach(
      (table) => {
        TableHeader.tables.push(new TableHeader(table));
      },
    );
    forTables('onScroll');
  }

.
After this is changed then the recalculate function is invoked as expected.The problem with this is that the table is still overflowing out of the details element as you can see in the SS.

Re #12
The current MR works only if we change table.sticky-enabled to table.position-sticky in this

Claro tableheaders are sticky even though it isn't initializing in tableheader.js, so that means that stickiness is being achieved

Claro moved away from using tableheader.js mid-2023 in favor of CSS positioning. 📌 Use position: sticky for views sticky table header Fixed . Even if this wasn't directly obvious, the fact that the tableheaders are sticky despite not being seen by tableheader.js strongly suggests the stickiness is being implemented without tableheader.js.

But before you go digging in that direction, it's probably worth confirming the issue as reported can even be reproduced in Claro. I can't reproduce it and I assume it works fine because it now uses CSS positioning.

From the looks of it there's nothing needed in Claro. Even if that was reported in the issue, it's always possible something changed in an update and the reporter might be using an earlier version of Drupal.

If you try a theme that isn't Claro, this does appear to still be an issue

While updating tableheader might fix it, perhaps using CSS positioning in the same manner as Claro could do the trick as well. I recommend seeing if there aren't already issues-in-progress for either of those before determining what to do here.