"Confluence Sortable Tables" system app wrongly sorting normal cells like the header.

Problem

When creating a table with more than 4 columns inside an expand macro the first row of the table below the header will turn into "cosmetic sorting buttons" that will sort the cells exactly like the header and mess up the table formatting.

In the example above you can see the same table copied/created outside of the expand macro functioning correctly.

After creating a number of pages reproducing the same behavior, when navigating normally in Confluence and then coming back to these pages to check up, the issue is gone showing a normal table without the buttons, so while the issue is easily reproducible this way, it appears to be showing randomly when viewing pages.

Steps to Reproduce

1- Create or Edit a Page

2- Add an Expand Macro

3- Create a Table with more than 4 columns

4- Have a table with sorting buttons on normal cells, that will break the formatting.

Expected Results

A normal formatted table with only the header sorting the cells

Actual Results

Cosmetic sorting buttons appear on the first row of the table

Observations

•  When I created the page with a Table with less than 4 columns inside the expand macro, the table didn't break, and the issue is not reproducible when viewing the page. HOWEVER, if I add an extra column to the table (4+ columns), and update the page, the issue appears again when seeing the page, and an even more weird scenario is that when we try and remove the extra column back, the table remains broken forever.

• When I keep navigating Confluence normally and come back to this New Page I've created in the example above, the table sometimes is broken with the issue reproduced, and sometimes not. And even without any editing or interaction on the page source code/format, the results shown are just random.

•  I also did a comparison with another example that I had of a Customer:

<p><ac:structured-macro ac:name="childtabs" ac:schema-version="1" ac:macro-id="e6217637-99c4-4ac3-a558-e8677f001c0e" /></p>

 
On the customer environment, the objective of this comparison was that the pages involved in the examples had some differences (no expand macros on the pages).

As mentioned above I was able to isolate and replicate using the confluence expand macro on the other example before, but on the Navitabs example, we didn't have the expand macro on the child pages, just tables and basic text, so when we accessed the child pages directly they were not broken, but when the same pages are "viewed as a preview" on the Parent page using Navitabs, somehow it breaks the tables the same way expand macro does, so there's a weird relation behind triggering this effect.

Workaround

For now, if possible avoid using tables inside Expand Macros and Navitabs plugin interactions with pages containing tables.

Other Notes

• I didn't see anything relevant on the browser developer tools, it appears to call this sort function exactly the same as the header does.

• Even when recording with browser Dev Tools, you don't see any "calls" on the network while sorting because everything is already loaded up.

• I believe there's something related to the way these tables are being rendered/viewed, and somehow it is reproducible randomly and inducible in some scenarios, like the Navitabs one and natively with the expand macros and no plugin installed.

• I also tried disabling each module of the Confluence Sortable Plugins system app individually and testing it separately. By doing so we don't see the issue but also lose the capacity to sort the table normally through Header, breaking the system app functionally purpose as a whole.

•  Issue was not reproducible on Confluence 7.19.6