Open Bug 524684 Opened 11 years ago Updated 2 years ago
The text for various options in the per-account "Synchronization & Storage" screen are confusing
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:220.127.116.11) Gecko/20090824 Firefox/3.5.3 Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:18.104.22.168pre) Gecko/20091023 Lightning/1.0pre Shredder/3.0pre Under Synchronization & Storage, one sees: - Message Synchronization Keep messages for this account on this computer (Advanced) - Disk Space To save disk space, downloading messages from the server and keeping local copies for offline use can be restricted by age size Synchronize all messages... etc. It is, to me, unclear from the wording, as well as the behavior of the preference, whether these are two different controls of the same option, or two different options. Reproducible: Always Expected Results: Parallel wording should be used to help reinforce that this is one option. For example, the text under "Message Synchronization" might read "Download messages for this account from the server for offline use use..." as the current "Disk Space" read. Alternately, the text under "Disk Space" might read "To save disk space, the messages kept on this computer for this account can be restricted..."
Summary: The text for various options in the per-account "Synchronization & Storage" screen are confusing and contradictory → The text for various options in the per-account "Synchronization & Storage" screen are confusing
Component: Preferences → Account Manager
OS: Mac OS X → All
QA Contact: preferences → account-manager
Hardware: x86 → All
Version: unspecified → Trunk
FYI. Bug 537943 is for improvement of "Advanced" button. xref. See bug 562589 comment #1 for summary of current behaviour of "Keep messages...". See bug 562589 comment #10 for rough sketch of auto-sync, offline-use, Download Now.
Depends on: 537943
Bug 537943 comment #17 is a proposal of improvements.
You need to log in before you can comment on or make changes to this bug.