Bug 371748 - KUrlCompletion resolves symbolic links before resolving relative paths
Summary: KUrlCompletion resolves symbolic links before resolving relative paths
Status: RESOLVED WORKSFORME
Alias: None
Product: frameworks-kio
Classification: Frameworks and Libraries
Component: URL navigator (show other bugs)
Version: 5.27.0
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: David Faure
URL:
Keywords:
Depends on:
Blocks: 305492
  Show dependency treegraph
 
Reported: 2016-10-27 15:50 UTC by Alex Bikadorov
Modified: 2022-12-29 05:24 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alex Bikadorov 2016-10-27 15:50:26 UTC
Usage case: Krusader is using a KUrlRequester to ask the user for the destination directory for a file move operation.

Now, if the base directory is a symlink then the completion for relative paths is always made for the link destination and not the symlink location.

E.g. if "/tmp/bin" is a link to "/bin" and the base directory for the URL completion is set with
> urlCompletion->setDir("/tmp/bin");
then the completion suggestion when typing ".." is always made for "/" ("/bin", "/boot", "/etc", ...) but it should show completion for "/tmp".

KUrlRequester->url() returns the unresolved url (e.g "/tmp/bin/..") and it can later be chosen what to do with it. But this is not possible for the url completion, so either changing the default behaviour or adding an option to set this in KUrlRequester or KUrlCompletion is fine.
Comment 1 Justin Zobel 2022-11-29 05:06:24 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 2 Bug Janitor Service 2022-12-14 05:12:51 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2022-12-29 05:24:35 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!