Bug 310628

Summary: Don't use arrow icons to show/hide details in the progress indicator
Product: [Applications] kmail2 Reporter: Bernd Oliver Sünderhauf <pancho.s>
Component: UIAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: normal    
Priority: NOR    
Version: 4.9.3   
Target Milestone: ---   
Platform: Chakra   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Bug Depends on:    
Bug Blocks: 303462    

Description Bernd Oliver Sünderhauf 2012-11-25 00:09:08 UTC 
When synchronizing IMAP folders (probably POP as well, but I don't use that), the progress indicator in the status bar displays an upward arrow.
Even if you know that the arrow is a details button, this is disturbing, as an upward arrow is strongly associated with uploading resp. synchronizing up.
In some circumstances (e.g. after hitting other bugs making you nervous about your data) this is even more disturbing: you know for sure that there is nothing to synchronize upwards, so you're fearing that kmail/Akonadi might do something with the data on your server that it shouldn't do.
Again, knowing doesn't help as our limbic system doesn't care.

Reproducible: Always



Expected Results:  
It would be expected that the arrow indicates whether currently data is being synchronized up resp. synchronized down. The progress details button should use a different icon. However, plus and minus wouldn't be better, as these are associated with adding resp. deleting items.
The best approach I can come up is a magnifier icon on a snap-in / snap-out button.
Comment 1 Denis Kurz 2016-09-24 17:55:05 UTC 
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
Comment 2 Denis Kurz 2017-01-07 21:58:52 UTC 
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.