Ticket #256 (defect)
Opened 3 years ago
Last modified 3 years ago
next actions with sensitive due-date doesn't automatically sorted with Ajax
Status: assigned
| Reported by: | mkutny@gmail.com | Assigned to: | bsag (accepted) |
|---|---|---|---|
| Priority: | lowest | Milestone: | 2.0 |
| Component: | Coding | Version: | 1.04 |
| Severity: | minor | Keywords: | |
| Cc: |
When I add new next action with due date set it goes to the bottom of the specified context unconditionally.
It's only gets sorted to a proper place of the list when I refresh the page.
Change History
04/22/06 10:17:20: Modified by bsag
- priority changed from normal to lowest.
- status changed from new to assigned.
- milestone set to 1.10.
05/19/06 00:44:37: Modified by anonymous
Why not sort on the client side with Javascript? Perhaps you could embed a sortable key in the return value that would assist in the client side sorting.
I'm not sure that there's much we can do about that because of the way that Ajax and the RJS templates work. We could re-render the whole context box, sorting it as we do so, but that would mean pulling in a lot more data than necessary, slightly negating the benefits of Ajax. I also think that it's a bit confusing if actions are shifting themselves around when you add them. If it's always added at the bottom, you know where it is.
I'll leave this active in case I think of some cunning plan for getting around it, but it's low priority.