1- Restart/boot your PC. 2- Shift+Del+Enter an item. Result: The file opens. Expected result: If the ONLY you thing you do between the Shift+Del and the confirmation pop up appearing is pressing Enter; the Enter input should be transferred to the "Delete permanently" once the pop up appears.
Just to confirm - your expected result here would be that a destructive action (permanently deleting a file) should be taken without the user explicitly taking an action on a visible prompt? This seems highly undesirable. Is there a long delay after rebooting between trying to delete a file and the confirmation appearing? Perhaps that is the real issue?
(In reply to John Kizer from comment #1) > Just to confirm - your expected result here would be that a destructive > action (permanently deleting a file) should be taken without the user > explicitly taking an action on a visible prompt? This seems highly > undesirable. > > Is there a long delay after rebooting between trying to delete a file and > the confirmation appearing? Perhaps that is the real issue? You mean that the confirmation window not appearing immediately is a bug? Is that window meant to be loaded with the whole system?
I’m asking if what you’re reporting as a bug is: “It takes an unusually long time for the confirmation dialog to appear after pressing Shift+Del for the first time” (also, where is said item? On the desktop?) Or “Keystrokes made after an action is taken that requires confirmation, but before the confirmation prompt appears, are not queued up and applied to that prompt once it does appear” Just intuitively, the former sounds like a bug, while the latter sounds like intentional behavior - so I’m just trying to understand the core issue at hand.
(In reply to John Kizer from comment #3) > I’m asking if what you’re reporting as a bug is: > > “It takes an unusually long time for the confirmation dialog to appear after > pressing Shift+Del for the first time” (also, where is said item? On the > desktop?) > > Or > > “Keystrokes made after an action is taken that requires confirmation, but > before the confirmation prompt appears, are not queued up and applied to > that prompt once it does appear” > > Just intuitively, the former sounds like a bug, while the latter sounds like > intentional behavior - so I’m just trying to understand the core issue at > hand. On the desktop, yes. The issue is the former, but since it seemed like the confirmation windows simply needs time to naturally load for the fist time, I had the idea of transferring the input.
Ok. Closing this one. Created Bug 502776