Activity log for bug #98950

Date Who What changed Old value New value Message
2007-03-30 10:10:32 Jeroen T. Vermeulen bug added bug
2007-04-02 01:44:39 Matthew Paul Thomas launchpad: status Unconfirmed Confirmed
2007-04-02 01:44:39 Matthew Paul Thomas launchpad: importance Undecided Medium
2007-04-02 01:44:39 Matthew Paul Thomas launchpad: statusexplanation
2007-04-02 07:41:22 Carlos Perelló Marín rosetta: statusexplanation This is nothing Rosetta specific, it happens with all tables using batching.
2007-04-02 20:32:22 Matthew Paul Thomas launchpad: statusexplanation This is nothing Rosetta specific, it happens with all tables using batching. The only example URL given is one from Translations. I'm pretty sure each example will need to be reported and fixed as a separate bug (see for example bug 2714, bug 35325), because a table column header doesn't know which URL parameter determines that column's content. Even if someone came up with a general fix, that fix would still need to be applied separately to each existing table of batched results.
2007-11-20 22:31:35 Matthew Paul Thomas description Some pages with search results and such are batched, breaking long result sets into smaller pages. Some pages have clickable column headers to influence client-side sorting of results. The two features don't play well together: click-sorting of columns only works on entries within a batch. It does not affect what entries are in which batch. Example: https://translations.beta.launchpad.net/ubuntu/feisty/+lang/nl This returns over a thousand entries, neatly batched in pages of 50 each. Now click on the header of the leftmost column (template name). The template names on the first page span the alphabet, now neatly sorted from "a..." to "y..." Now go to the second page and do the same: here, too, the template names span the alphabet. Even the very last page of results has entries from "b..." to "z..." A user who sorts results by clicking on a column header probably expects the entire result set to be re-sorted, not just the data that happens to be visible on the current page. The first page would show only templates whose names start with "a," and the last would only show the ones at the very end of the alphabet. https://translations.launchpad.net/ubuntu/feisty/+lang/nl This returns over a thousand entries, neatly batched in pages of 50 each. Now click on the header of the leftmost column (template name). The template names on the first page span the alphabet, now neatly sorted from "a..." to "y..." Now go to the second page and do the same: here, too, the template names span the alphabet. Even the very last page of results has entries from "b..." to "z..." A user who sorts results by clicking on a column header probably expects the entire result set to be re-sorted, not just the data that happens to be visible on the current page. The first page would show only templates whose names start with "a," and the last would only show the ones at the very end of the alphabet.
2007-11-20 22:31:35 Matthew Paul Thomas title Batched result pages break "click-sortable" columns Column sorting doesn't work on distribution series language pages
2009-10-31 14:06:56 Данило Шеган rosetta: importance Medium High
2009-10-31 14:07:16 Данило Шеган summary Column sorting doesn't work on distribution series language pages Sorting doesn't work on distribution series language pages
2009-10-31 14:07:29 Данило Шеган tags ui
2011-12-19 09:05:11 Robert Collins launchpad: importance High Low