Closed Bug 8721 Opened 25 years ago Closed 25 years ago

Search messages: need max limit for added criteria lines

Categories

(SeaMonkey :: MailNews: Message Display, defect, P3)

defect

Tracking

(Not tracked)

VERIFIED WONTFIX

People

(Reporter: laurel, Assigned: alecf)

Details

Using jun22 m8 builds on linux rh5.2, NT 4.0 and Mac OS 8.51 You are currently able to add lots of criteria lines in the Search Messages dialog. Although this is not (yet?) spec'd for 5.0, the limit in 4.x was five criteria lines.
QA Contact: lchiang → laurel
Status: NEW → ASSIGNED
Target Milestone: M10
I don't know why there was a limit in 4.x David, the UI is basically unlimited, can you think of a reason we need to add a limit in 5.0?
I think there was a limit because of the UI dialog size. If there are too many criteria to choose from, then it wouldn't fit in the UI dialog and dialogs don't normally have scroll bars to scroll the dialog. Perhaps the 4.x Search UI spec mentions this.
yes, there's no backend reason to limit the number of criteria.
FYI -- the Nova UI Search & Filter Spec states: "More/Fewer: These buttons expand and contract the search criteria area. There can be at most five criteria rows and at least one criteria row. When five rows are displayed, the More button is disabled. When one row is displayed, the Fewer button is disabled." As I mentioned, there is no revised Search spec info for 5.0, but the current Filters spec states a limit of 5 "conditions" or criteria.
Target Milestone: M10 → M14
search->M14
Search won't be in PR1, so I don't think this bug needs to be fixed for PR1
Target Milestone: M14 → M15
I don't think_we_need_a_limit-this_should_be_just_invalid,or_say_there's_no_limit,assuming_the_dialog will expand.
Target Milestone: M15 → M16
search bugs -> M16
decided that we wouldn't do this for filters, so we won't do this for search either.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → WONTFIX
mark verified.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.