User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2) Gecko/20100115 Firefox/3.6 (.NET CLR 3.5.30729) Build Identifier: This is not too critical but it would good to have a simple way to differences these interfaces. This had to be done in tb30 because this change was made in tb2->tb3. Because interfaces of tb30 are frozen it would be good to fix it in tb31. interface nsMsgSearchOp has new and changed constants: new: const nsMsgSearchOpValue IsntEmpty = 18; /* primarily for tags */ const nsMsgSearchOpValue Matches = 19; /* generic term for use by custom terms */ const nsMsgSearchOpValue DoesntMatch = 20; /* generic term for use by custom terms */ changed: tb2: const nsMsgSearchOpValue kNumMsgSearchOperators = 18; /* must be last operator */ tb3: const nsMsgSearchOpValue kNumMsgSearchOperators = 21; /* must be last operator interface nsMsgSearchScope has new constants new: /// IMAP and NEWS, searched using local headers const nsMsgSearchScopeValue onlineManual = 13; /// local news + junk const nsMsgSearchScopeValue localNewsJunk = 14; /// local news + body const nsMsgSearchScopeValue localNewsBody = 15; /// local news + junk + body const nsMsgSearchScopeValue localNewsJunkBody = 16; Reproducible: Always
(In reply to comment #1) > Created an attachment (id=432768) [details] > Proposed patch for nsMsgSearchCore.idl Palo can you set the review and super-review request flags ?
Yes, I can. Sorry, I forgot.