Last modified: 2011-05-06 22:34:18 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 28859 - sortable tables mix up cells when rowspans are present
sortable tables mix up cells when rowspans are present
Status: RESOLVED DUPLICATE of bug 8028
Product: MediaWiki
Classification: Unclassified
JavaScript (Other open bugs)
All All
: Unprioritized normal (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2011-05-06 20:11 UTC by pietz
Modified: 2011-05-06 22:34 UTC (History)
2 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Description pietz 2011-05-06 20:11:12 UTC
The sortable flag in wikitables is very buggy implemented in javascript when sorting tables with rowspans. The table cells are placed nearly randomly in the table after a few clicks.

Seems like a problem in the sort algorithm. I tried it with Firefox and Chrome.
Comment 1 Brion Vibber 2011-05-06 21:14:32 UTC
Do you have an example page?
Comment 2 pietz 2011-05-06 22:26:26 UTC
I just set one up for you on my discussion page:

Just play a bit with the sort buttons and then see the third column popping up in that two columned table?
Comment 3 Krinkle 2011-05-06 22:33:28 UTC

*** This bug has been marked as a duplicate of bug 17515 ***
Comment 4 Krinkle 2011-05-06 22:34:18 UTC
Fixed in trunk. Will be deployed with 1.18

*** This bug has been marked as a duplicate of bug 8028 ***

Note You need to log in before you can comment on or make changes to this bug.