-
-
Notifications
You must be signed in to change notification settings - Fork 538
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
next actions with sensitive due-date doesn't automatically sorted with Ajax #256
Comments
On April 4, 2006 at 19:17:20 (+0800), Anonymous commented: 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. |
On May 5, 2006 at 09:44:37 (+0800), Anonymous commented: 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. |
This is also an issue when the context is changed (from #938). |
Related to #393 |
I'm working on this, and have a working prototype. My approach is to add a Is this a feasible approach? |
Migrated from the original issue at https://www.assembla.com/spaces/tracks-tickets/tickets/256
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.
Originally reported by Anonymous on April 4, 2006 at 21:01:30 (+0800)
The text was updated successfully, but these errors were encountered: