Created attachment 166237 [details] Dragging location bar to left side SUMMARY *** In split view mode the location bar of the right side adds a separator and becomes drag-able across toolbar *** STEPS TO REPRODUCE 1. Open Dolphin file manager. 2. Open Split view mode 3. Look at the right hand side of the location bar, you will see a separator. 4. Take your cursor to the separator and now with left click you can drag the location bar all the way to the left or right. OBSERVED RESULT You can drag location bar on split view. EXPECTED RESULT You should not be able drag toolbar elements across toolbar. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.5.0-21 KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION 1. Maybe this is intended design so people can use more space to edit file path. If that is the case feel free to close the bug. 2. You can hide separator in breeze style by unchecking "draw toolbar icon separator" by this split view separator will be persistent even if you do so.
I can reproduce this on arch with plasma 6 and also find it a bit weird
A possibly relevant merge request was started @ https://invent.kde.org/system/dolphin/-/merge_requests/750
The developers say this behavior is intentional, so as to allow more space for checking the path (see https://invent.kde.org/system/dolphin/-/merge_requests/750). Do you find the moveable separator feature useful, or do you find it strange and inconvenient? Your input is welcome!
I honestly don't really care about it. Its not really discoverable, so I never noticed it exists until this bug report. Now that I know about it, it seems useful in very specific situations, so not removing it for these makes sense I guess. But it also does not really matter, so if it adds maintenance burden, it can be removed in my opinion.
(In reply to Tammes Burghard from comment #4) > I honestly don't really care about it. Its not really discoverable, so I > never noticed it exists until this bug report. Now that I know about it, it > seems useful in very specific situations, so not removing it for these makes > sense I guess. But it also does not really matter, so if it adds maintenance > burden, it can be removed in my opinion. I think that's a fair assessment. It's not all that discoverable, so its usefulness is limited. If it ever becomes difficult to keep it, we shouldn't put too much work into keeping it. As it stands though, it would require more code to disable it than to simply keep it as is.