https://bugs.kde.org/show_bug.cgi?id=440663

Luke Horwell <c...@horwell.me> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |c...@horwell.me

--- Comment #31 from Luke Horwell <c...@horwell.me> ---
For context, I'm gathering that this regression came to be because of this
behaviour change:

> What we want to happen is Dolphin to focus the window we have with the file 
> selected.
> -- https://invent.kde.org/frameworks/kio/-/merge_requests/554

In my opinion, we should go back to the previous KDE 5.22.4 behaviour which is
to compress/extract in the background. I'm not sure if this "we want to focus
the window" idea is intended to interrupt the user, since even fixing the new
tab/window regression sounds like a new problem would be introduced: I could be
in another program doing other things and Dolphin jumps to the top (like it
already gets in the way now). Even flashing in the 'taskbar' might not be
suitable, because I may have changed folder/tabs after a long
compression/extraction has completed. At the very least, an option to turn off
any focus/attention grabbing feature would be appreciated.

If the idea is to help the user return to the folder, instead of trying to
bring the window into focus, the notification that reads "Compressing a file
(Finished)" & "Extracting Files (Finished)" might be a better outlet. There's
already a button for "Open Containing Folder" for the extraction, but there
isn't one for the compression notification.

Currently in 5.23.3 / Frameworks 5.88, there are similar instance-related bugs,
and possibly causing confusion and/or may be related to this change:
- When compressing a file, and the window is closed, Dolphin crashes and the
compression doesn't complete.
- When extracting a file, and is cancelled via notification, Dolphin continues
to extract in the background.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to