Bug 409738

Summary: Kmail save as dialog defaults to save on enter
Product: [Applications] kmail2 Reporter: Martin van Es <bugs>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Severity: normal CC: nate, poprocks
Priority: NOR    
Version: 5.10.3   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:

Description Martin van Es 2019-07-12 08:04:42 UTC
When saving an attachment, pressing enter on a directory both activates the save button and enters the directory, resulting in unintended saves in the wrong folder if the planned destination folder is some levels deeper.

I combine mouse and keyboard as much as possible, so when saving an attachment from kmail I select the top-level directory I want to enter in and navigate using arrow keys and enter to descend into the right directory.

Since a couple of revisions this is not possible anymore as can be read from this bug: https://bugs.kde.org/show_bug.cgi?id=407634

The strange thing now is, that it's solved for the ksavedialog example, but not for kmail.

1. Receive mail with attachment in kmail
2. Click attachment and choose save-as
3. Select top-level directory and try to descend into this directory using enter key

It wil save the file into the selected directory

Descending into the selected directory to continue searching the correct destination using arrow keys

Operating System: Kubuntu 19.04
KDE Plasma Version: 5.16.3
KDE Frameworks Version: 5.59.0
Qt Version: 5.12.2
Kernel Version: 5.2.0
OS Type: 64-bit
Processors: 4 × Intel® Core™ i7-7500U CPU @ 2.70GHz
Memory: 15.5 GiB of RAM
Comment 1 Logan Rathbone 2019-10-09 19:37:16 UTC
This seems to be a broader issue and not specific to kmail.

See:  https://bugs.kde.org/show_bug.cgi?id=412737

The fixes described in 407634 don't seem to be far enough reaching.

Using:  KDE Plasma Version: 5.16.5, KDE Frameworks Version: 5.62.0, Qt Version: 5.13.1

Slackware Current using packages from AlienBob's "ktown" repo (which use little to no patching from upstream).
Comment 2 Nate Graham 2019-10-09 19:48:49 UTC
Nice catch.

*** This bug has been marked as a duplicate of bug 412737 ***