Bug 453289

*** Bug 453176 has been marked as a duplicate of this bug. ***

@Nate,
I don't think this problem is the same. For me Dolphin doesn't select anything when Up is being used.

*** Bug 453347 has been marked as a duplicate of this bug. ***

> I don't think this problem is the same. For me Dolphin doesn't select anything when Up is being used.

It's kind of "implicitly selected". It's not fully highlighted with a blue background, but it is underlined with a blue line, and it behaves as selected at least in that, if you hit Enter, it's the one you go into.

The problem, anyway, is that the child folder you're coming from is not selected, and it should (and used to be), so it does seem to be the exact same issue described in the other bugs.

BTW when you say "parent" I think you mean "child". If P is the parent of C and C is the child of P, you navigate from C to P and the one that fails to be selected is C.

Yes, I now checked it and it's indeed underlined, you're right :)

I don't know if it will be parent or child (I'm a non-native speaker), but I think everybody realized what the problem is :)

I can not reproduce this bug on current master. It seems to select the child folder one has emerged from correctly after using the "Up" action.

>It's kind of "implicitly selected". It's not fully highlighted with a blue background,
>but it is underlined with a blue line, and it behaves as selected at least in that,
>if you hit Enter, it's the one you go into.

This is actually the behaviour I would prefer in general. We have a bug report that wishes for this behaviour to be implemented everywhere. See https://bugs.kde.org/show_bug.cgi?id=424723.

It is true that the behaviour reported here is currently inconsistent and I don't know what caused this but I would rather see https://bugs.kde.org/show_bug.cgi?id=424723 fixed than this one. But since we already seem to be back to the old behaviour on master, I guess this will have to wait.

> This is actually the behaviour I would prefer in general. 

To clarify, the folder that gets underlined now (after this regression has appeared) is the first one in the folder, NOT the one you came from.
If you suggest that *the folder you came from* gets just underlined (like the first folder is now) instead of fully selected (like the folder you came from used to be), I'm not sure of all the implications of that, but I think it's fine, as long as, at least:
- pressing enter will enter that folder
- using the right arrows will select the folder next to that one.
which I think is what would happen, since it's what now happens to the first folder, which gets underlined.

Can confirm, it's always the first folder that gets underlined, not the folder I navigated from using UP. Also I'm sure it was working correctly a few months ago, so it must be a recent regression.

>To clarify, the folder that gets underlined now (after this regression has appeared)
>is the first one in the folder, NOT the one you came from.

Oh okay. I had missed this.

>If you suggest that *the folder you came from* gets just underlined (like the first folder is now)
>instead of fully selected (like the folder you came from used to be), I'm not sure of all the
>implications of that, but I think it's fine, as long as, at least: […]

Yes, that is what the other bug reporter is suggesting and I am agreeing with. But now that I saw that the old behaviour is already back in the current master development branch, this is now not related to this bug report anymore.

> I can not reproduce this bug on current master. It seems to select the child
> folder one has emerged from correctly after using the "Up" action.

I installed dolphin-git-22.04.0.r67.g0fc218fd2-1 from AUR on Arch Linux, which is supposed to be the current master, and the bug still reproduces. The folder that's underlined is always the first, and not the one I navigated up from.

I can now also reproduce the bug on master. Not sure why I wasn't able to reproduce it the last time I tried.

It's a crucial behaviour and without it it's a nightmare. Let's hope for a quick fix.

>I can now also reproduce the bug on master.
>Not sure why I wasn't able to reproduce it the last time I tried.

The reason why I wasn't able to reproduce with Dolphin master was that the regression was introduced by a change in frameworks and not by a change in Dolphin. Since I had updated frameworks since then I was suddenly able to reproduce the bug on master.

I was successful in identifying the faulty commit in the KIO framework: https://invent.kde.org/frameworks/kio/-/commit/fdacbf4e290c856a72a5988f5a612360a76af896 It was the first commit I tried because it looked like it might be the reason.

I am therefore moving this bug to KIO now since framework changes shouldn't cause regressions in application code. I'll also let the person responsible for this regression know that this bug exists. I hope they will be able to fix it quickly.

@Felix Ernst
Thank you so much!

You are welcome!

A possibly relevant merge request was started @ https://invent.kde.org/frameworks/kio/-/merge_requests/862

(In reply to Bug Janitor Service from comment #16)
> A possibly relevant merge request was started @
> https://invent.kde.org/frameworks/kio/-/merge_requests/862

the patch fixes the bug for me

*** Bug 455035 has been marked as a duplicate of this bug. ***

Git commit 75c62a2d436b359bde211b7255895ed04595ce20 by Nate Graham, on behalf of Janet Blackquill.
Committed on 08/06/2022 at 19:12.
Pushed by ngraham into branch 'master'.

KCoreUrlNavigator: add urlSelectionRequested signal

M  +3    -0    src/filewidgets/kurlnavigator.cpp
M  +3    -0    src/gui/kcoreurlnavigator.cpp
M  +12   -0    src/gui/kcoreurlnavigator.h

https://invent.kde.org/frameworks/kio/commit/75c62a2d436b359bde211b7255895ed04595ce20