This bug is to track the implementation of the offline dialog that allows you to choose what types of folders you want to sychronize and allows you to do the synchronization.
marking nsbeta1+ and moving to mozilla0.9
Priority: -- → P1
Target Milestone: --- → mozilla0.9
changing QA assigned to gchan.
QA Contact: hong → gchan
Change to Mozilla0.9.1
Target Milestone: mozilla0.9 → mozilla0.9.1
move to 0.9.3, backend pendendent.
Depends on: 65209
Target Milestone: mozilla0.9.2 → mozilla0.9.3
I am not quite clear where backend handles hostname, folder name, # messages synch-ed. Do we need some implementation function, such as onStateChange(), onProgressChange(), like the implemention in nsMsgComposeProgress.cpp to support nsMsgProgress.cpp functions for Synchronization? Please advise.
Target Milestone: mozilla0.9.3 → mozilla0.9.4
This bug was originally logged for synchronize dialog such as folder selection, sync type selection which had been implemented before .9.2. What left is the sync progress dialog only which depends on further implementation at the backend for nsMsgProgress functions such as onStateChange(), onProgressChange(), an example is like the implemention in nsMsgComposeProgress.cpp for compose/send messages.
I would suggest to move this bug to futue or next release until the backend is ready for the synchronization progress dialog( this is only for the progress dialog). The similar implenmentation for the UI side is like sendProgress.dtd, sendProgress.xul and sendProgress.js but the functionalities need to be provided by the backend and the UI is invoked from the backend. For detail info, please see my previous comments or ask JFD and David.
Reassigning 0.9.4 Offline IMAP UI bugs to David; TFV 0.9.5.
Assignee: dianesun → bienvenu
mscott, have you done the work I need to do this? I.e., the generic progress dialog work that supports nsIMsgWindow
Keywords: nsenterprise+ → nsenterprise-
moving to 1.0 - turns out that the work needed for this isn't done, and I'm not sure we're going to have time to do it.
Target Milestone: mozilla0.9.5 → mozilla1.0
Bugs targeted at mozilla1.0 without the mozilla1.0 keyword moved to mozilla1.0.1 (you can query for this string to delete spam or retrieve the list of bugs I've moved)
Target Milestone: mozilla1.0 → mozilla1.0.1
Status: NEW → ASSIGNED
Target Milestone: mozilla1.0.1 → mozilla1.0
Keywords: nsbeta1+ → nsbeta1-
Target Milestone: mozilla1.0 → mozilla1.2
this was fixed a long time ago...
Status: ASSIGNED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.