Tickets :: [#6515] IMP's search element removal should be like Ingo's search element removal

Summary	IMP's search element removal should be like Ingo's search element removal
Queue	IMP
Queue Version	HEAD
Type	Enhancement
State	Resolved
Priority	1. Low
Owners	selsky (at) columbia (dot) edu
Requester	liamr (at) umich (dot) edu
Created	3/21/08 (6594 days ago)
Due
Updated	3/21/08 (6594 days ago)
Assigned
Resolved	3/21/08 (6594 days ago)
Milestone
Patch	No

03/21/2008 10:06:14 PM	Matt Selsky	Comment #2 Assigned to Matt Selsky State ⇒ Resolved	Reply to this comment
Fixed in HEAD and 4.2-rc4.

03/21/2008 09:29:11 PM	Chuck Hagenbuch	State ⇒ Accepted

03/21/2008 07:34:41 PM	liamr (at) umich (dot) edu	Comment #1 Priority ⇒ 1. Low New Attachment: imp_search.diff Patch ⇒ No Milestone ⇒ Queue ⇒ IMP Summary ⇒ IMP's search element removal should be like Ingo's search element removal Type ⇒ Enhancement State ⇒ New	Reply to this comment
IMP lets you search for messages based on certain criteria and display the results. Ingo lets you search for messages based on certain criteria and file messages based on the results. IMP's search interface (imp/search.php), and Ingo's rules creation interface (ingo/rule.php) are quite similar.. yet, to delete search elements in IMP, the UI uses "close_img", while to delete elements in Ingo, the UI uses "delete_img". The decision for Ingo makes more sense. For UI consistency, IMP should be made to match.