Used 05-10-12-M16 commercial build The Server advance preference UI is available, we should implement check/uncheck "show only subscribe folders" functionality from IMAP Server Advance Preference 1) Login to an IMAP mail account 2) From the Account setup, select the server setting & click advanced button to bring up the server advanced dialog 3) Actual results: Check or uncheck the "show only subscribe folders" doesn't make any change. Expected results: Check or uncheck "show only subscribe folders" functionality should reflect the change from IMAP Server Advance Preference Addtional Info: Mozilla seems to be operating in a "subscribed" mode only. If not using subscription we should list all folders.
I mean: Check or uncheck "show only subscribe folders" functionality from IMAP Server Advance Preference should reflect the change on the folder pane.
I am thinking this should be a feature bug.
This will be an easy fix once I fixed bug 39262.
bug 39262 is fixed, is this one essential for ship? Looks like "correctness" (nsbeta3 keyword)to me.
There has to be some fix made here. Either make the checkbox work or remove the checkbox / text from preferences.
Nominating and adding Correctness keyword.
+ per mail triage Remove the UI for this.
I think I'll just make it work, since the backend now supports it. Don't know why removing the UI is better than making it work, since they should be the same amount of work.
This *is* implemented, and works fine, as long as you shutdown and restart. The remaining work is to make it update the folder view with either all folders or just the subscribed folders, depending on the user's choice. I'll look at that, but I think we can ship with it as is.
I think the current behavior you describe is fine, David. If necessary, we can release note that the user has to restart. I'll remove nsbeta3+ for consideration of a -.
mail triage marking nsbeta3-. current behavior is fine.
changing summary to reflect remaining bug.
removing the mail1 keyword
Removing the mail1 keyword.
if this is easy, we should fix it.
changing milestone to unknown. It will get changed back when we figure out what milestone to put this bug in.
marking nsbeta1-. This will not affect many users.
Is there any chance the bug will be fixed in Mozilla-1.7 ?
Not planning on working on this - it's not a commonly used feature and the work-around is to restart. The fix would probably be to detect when the user changes this pref and clear the sub-folder list for the root folder of the server, and clear the havediscovered folders flag, and force a rediscovery operation.