Bug 426353 - "Send via Email" on a webdav/SMB share appends URL not an attachment.
Summary: "Send via Email" on a webdav/SMB share appends URL not an attachment.
Status: CONFIRMED
Alias: None
Product: frameworks-purpose
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 5.70.0
Platform: Fedora RPMs Linux
: NOR minor
Target Milestone: ---
Assignee: Aleix Pol
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-09-09 20:53 UTC by cberlinger
Modified: 2022-02-07 14:06 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description cberlinger 2020-09-09 20:53:25 UTC
SUMMARY
When using dolphin to access a private LAN file share via webdav, SMB or presumably other kio connection types, it is not possible to attach a file to an email via the right-click service context menu "Share -> Send via Email". Instead a URL to the file is added to the body of the KMail email message. However if you drag the file out of dolphin and into the body of the email, when you release the mouse button an option is presented to attach the file or add a URL into the email. Should the default for "Send via Email" be set to an attachment, not a URL?      

STEPS TO REPRODUCE
1. Have Kmail installed and configured and then open Dolphin
2. Navigate to an SMB share and find a file you want to send in an email.
3. Right-click on the file to pen the context menu, and go to the Share menu and select "Send via Email"
4. KMail composer will open and a URL will be added to the bottom of the email.

OBSERVED RESULT
A URL will be in the KMail instead of the desired attached file.

EXPECTED RESULT
An attached file should be in the email.

SOFTWARE/OS VERSIONS
Operating System: Fedora 32
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.70.0
Qt Version: 5.14.2
Kernel Version: 5.8.4-200.fc32.x86_64
OS Type: 64-bit
Processors: 4 × Intel® Core™ i5-4690K CPU @ 3.50GHz
Memory: 15.5 GiB of RAM

ADDITIONAL INFORMATION
Comment 1 Aleix Pol 2020-09-11 09:49:05 UTC
I wonder what's the right way of fixing this issue.

At the moment it's using QUrl::isLocalFile(). Elvis, which way could we use to decide whether to bring the file?
Comment 2 Elvis Angelaccio 2020-09-18 18:01:16 UTC
Well any kio protocol should provide at least read-only support to the files. I guess we can try to remove that QUrl::isLocalFile() check?
Comment 3 Nicolas Fella 2022-02-07 14:06:51 UTC
It's a bit of a tricky one...

e.g. for http://foo.bar/index.html we want to send the URL as text, not the index.html file as attachment