| Summary: | Allow using web addresses as image source | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] frameworks-kio | Reporter: | Antti Savolainen <antti.savo> |
| Component: | Open/save dialogs | Assignee: | KIO Bugs <kio-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | wishlist | CC: | kdelibs-bugs-null, nate |
| Priority: | NOR | ||
| Version First Reported In: | 6.2.0 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Antti Savolainen
2024-06-10 16:19:24 UTC
You can. :) If you can't, it's either a bug in our code, or else you've actually using the GNOME/GTK file dialog which doesn't have this feature. Am I doing something wrong in this demonstrative video or is the feature bugged? https://youtu.be/p_wRL4t7Cmw Well, the target app has to be capable of accepting URLs as input. :) In this case Firefox appears to be only accepting local files. Or maybe it's not Firefox and it's actually bugzilla that won't accept a URL for this field. Either way, the file dialog did its part, but the output it handed off to the app itself needs to be handled by the app. I see. Would it be possible to create a feature that downloads the file in the URL to /tmp/ for example and then adds that as input? How would the system know that the client is going to reject a URL, though? Yeah, I didn't know if there was a mechanism to detect that, which is why I asked. Maybe a system setting that toggles between passing the URL and always downloading the file before upload? It was a rhetorical question; there isn't a way. :) Working around that by always downloading would work, but waste network resources and time--particularly for large files. Adding a user-facing setting to switch between the two does not make sense becaus eusers would be unable to determine whether to use it or not. This is the kind of internal thing that the system itself needs to decide on. |