[dolphin] [Bug 507619] New: When split view is enabled, opening a folder externally opens 2 of the same folder in a new split view tab.
alk
bugzilla_noreply at kde.org
Tue Jul 29 03:53:07 BST 2025
https://bugs.kde.org/show_bug.cgi?id=507619
Bug ID: 507619
Summary: When split view is enabled, opening a folder
externally opens 2 of the same folder in a new split
view tab.
Classification: Applications
Product: dolphin
Version First unspecified
Reported In:
Platform: CachyOS
OS: Linux
Status: REPORTED
Severity: wishlist
Priority: NOR
Component: split view
Assignee: dolphin-bugs-null at kde.org
Reporter: kde.agonize330 at passmail.net
CC: kfm-devel at kde.org
Target Milestone: ---
SUMMARY
When split view is enabled, opening a folder externally opens 2 of the same
folder in a new split view tab. This is because tabs control both panes. My
proposed solution is to allow each pane of the split view to have its own tabs.
This would allow allow new folders opened externally to immediately be used
with the 2nd pane that was open already, instead of getting 2 panes of the same
new folder. Each pane should separately be able to switch tabs.
STEPS TO REPRODUCE
1. set "open in split view" to true
2. open a folder externally (i.e. "browse files" from steam or "open folder" in
about:profiles in firefox)
3. dolphin opens a new tab, where both split view panes are the same new
folder. Then user must choose one pane and navigate back to whatever folder
they were working from before continuing.
I want to specify that this isn't necessarily a feature request for per-pane
tabs (as nice as that would be) but a request to change the behavior of opening
duplicate folders in 2 panes when opened externally, which isn't very useful.
Per-pane tabs would fix this, but isn't my core report here. Maybe the folder
could just open in the current/active pane instead of creating a new tab.
Operating System: CachyOS Linux
KDE Plasma Version: 6.4.3
KDE Frameworks Version: 6.16.0
Qt Version: 6.9.1
Graphics Platform: Wayland
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the kfm-devel
mailing list