Open Bug 101808 Opened 23 years ago Updated 2 years ago

add serverChangeInvalidatesFolders to nsIMsgProtocolInfo and fix onServerChanged() in msgMail3PaneWindow.js to use it

Categories

(MailNews Core :: Backend, defect)

x86
All
defect

Tracking

(Not tracked)

People

(Reporter: sspitzer, Unassigned)

References

(Depends on 1 open bug)

Details

add serverChangeInvalidatesFolders to nsIMsgProtocolInfo and fix onServerChanged
() in msgMail3PaneWindow.js to use it

when I landed #101640, I made it just check the type, and that's a hack.

an attribute on nsIMsgProtocolInfo and not nsIMsgIncomingServer is because this 
attribute is the same for all servers of that type.  (all imap and news servers 
would return true, all other existing protocol types [pop3, none, movemail] 
would return false).
for a related bug about checking against type, see #63369
Depends on: 63369
QA Contact: esther → stephend
Product: MailNews → Core
sorry for the spam.  making bugzilla reflect reality as I'm not working on these bugs.  filter on FOOBARCHEESE to remove these in bulk.
Assignee: sspitzer → nobody
Filter on "Nobody_NScomTLD_20080620"
QA Contact: stephend → backend
Product: Core → MailNews Core
OS: Windows 2000 → All
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.