Page MenuHomePhabricator

tablesorter has trouble exploding rowspans with row header cells
Closed, ResolvedPublic



this probably goes wrong because the cell that needs exploding is a TH instead of a TD.

Version: 1.21.x
Severity: major



Event Timeline

bzimport raised the priority of this task from to High.Nov 22 2014, 12:49 AM
bzimport set Reference to bz41889.
bzimport added a subscriber: Unknown Object (MLST).

(In reply to comment #2)

Fixed by Ibe4cc7e9.

No, it wasn't. That fixes a different bug.

A minimal test case for this bug seems to be the following table

{| class="wikitable sortable"


! foo bar baz !! n


!rowspan=2| foo


When the rowspans are exploded, both rows should have "foo" in the first cell, "bar" in the second, and "baz" in the third. But currently the second row will get "baz" in the second cell and "bar" in the third.

Gerrit change 34104 should fix it, plus a number of similar problems when row or colspans are used in creative ways.

Done. I seldom know who exactly to add, so I usually forget. (Gerrit Change Icb674f7eece053435ca9525d45709579df14cc74) | Code-Review: Reviewed:+2 Patch Set 8: Code-Review+2

OK, it can be merged, then. I would do it myself, except that the unit test file has a fairly large merge conflict. [by] (Gerrit Change Icb674f7eece053435ca9525d45709579df14cc74) | Patch Set 8: -Verified

Starting gate-and-submit jobs. [by] (Gerrit Change Icb674f7eece053435ca9525d45709579df14cc74) | Code-Review: Verified:-1 Patch Set 8: Verified-1

Build failed

This change was unable to be automatically merged with the current state of the repository. Please rebase your change and upload a new patchset. [by]

This is merged in -wmf12 and -wmf12 is in the process of being deployed across all WMF sites (should be done by end of next week). Closing.