| Summary: | [search] Click on column name to change sort order | ||
|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | John Arthorne <john.arthorne> |
| Component: | Client | Assignee: | libing wang <libingw> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | libingw, malgorzata.tomczyk, mamacdon, simon_kaegi, susan |
| Version: | 0.3 | ||
| Target Milestone: | 4.0 M1 | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
| Bug Depends on: | 360275 | ||
| Bug Blocks: | |||
|
Description
John Arthorne
*** Bug 359849 has been marked as a duplicate of this bug. *** I completely agree. The option approach is just a temporary solution for self-hosters. In bug 360275, I had some discussions with Susan, where we wanted a consistent UI for sorters. Susan, I put the target to M2, what do you think? (In reply to comment #2) > I completely agree. > The option approach is just a temporary solution for self-hosters. > In bug 360275, I had some discussions with Susan, where we wanted a consistent > UI for sorters. > Susan, I put the target to M2, what do you think? The blocking bug is assigned to me for 0.4 (so M2) but I may need some help from simply a time standpoint. I talked to Gosia early in 0.4 about helping, we'll check in during M2 and see what's on everyone's plate. *** Bug 386047 has been marked as a duplicate of this bug. *** I'm going to take a look. I'm doing a lot of API cleanup and code refactoring in the explorers/renderers/models and will put a sort mechanism in the model. Then the remaining work would be to implement the up/down column headings and a way to specify in the renderer that you want these to appear. See also bug 389529. moving out of 1.0, I was being too optimistic. given that sorting is already an option in the search page now, and clicking on column will redo the search (request server again), there is no need to trigger the resort from the result pane. |