[dolphin] [Bug 461739] New: Switching from Dolphin window while renaming from shortcut makes focus to leave current item

bugzilla_noreply at kde.org bugzilla_noreply at kde.org
Sat Nov 12 18:58:02 GMT 2022


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

            Bug ID: 461739
           Summary: Switching from Dolphin window while renaming from
                    shortcut makes focus to leave current item
    Classification: Applications
           Product: dolphin
           Version: 22.08.3
          Platform: OpenSUSE
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: dolphin-bugs-null at kde.org
          Reporter: tustamido at yahoo.com.br
                CC: kfm-devel at kde.org
  Target Milestone: ---

STEPS TO REPRODUCE
1. Press F2 or the other shortcut you have assigned to rename selected item
(file or folder).
2. Switch focus away from Dolphin by clicking over other window or pressing
Alt+Tab (supposing that's your shortcut to select a different window).
3. Switch focus back to Dolphin without directly clicking its window, so press
Alt+Tab instead or use the desktop panel.

OBSERVED RESULT

The focused element will be current tab (you can see it outlined) i.e. if you
press side arrow keys you'll activate a different tab (assuming there's more
than one open in current Dolphin window).

EXPECTED RESULT

Focus should remain on selected item (file/folder) so that arrow keys should
select previous/next item.

Note: from my experience, the result is very different if you triggered Rename
by using context-menu item. That way the renaming process doesn't end when you
select a different window, so this bug doesn't happen. This bug only happens
when I trigger Rename by pressing the shortcut (F2). 

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: openSUSE Tumbleweed
(available in About System)
KDE Plasma Version: 5.26.3
KDE Frameworks Version: 5.99.0
Qt Version: 5.15.7

ADDITIONAL INFORMATION
Wayland

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the kfm-devel mailing list