AzureStorageExplorer icon indicating copy to clipboard operation
AzureStorageExplorer copied to clipboard

Right click inside text inputs does NOT give context menu for Copy & Paste

Open golfalot opened this issue 5 years ago • 3 comments

Storage Explorer Version: March 2021 (Version 1.18.1) Build Number: 20210304.5 Platform/OS: Windows 10 Architecture: x64 Regression From: not known

Bug Description

Azure Storage Table -> Query -> Value input -> no right click context menu displayed

Steps to Reproduce

Open Azure Storage Table Query Right click in Value text field as fi to copy and paste

Expected Experience

Context menu with Copy & Paste

Actual Experience

Nothing happens. CTRL+V / CTRL+C works fine

Additional Context

golfalot avatar Mar 12 '21 16:03 golfalot

Same for dialog box "Connect to Azure Storage", you can't right click and paste a SASUri into "Blob container or directory SAS URL", thus, if you have a SASUri in the clipboard, you can only click the box and use the keyboard (CTRL+C) to paste the SAURI. For highly automated actions such as copying from somewhere to the mentioned box, going to the keyboard when you are working with the mouse it's a significant slowdown. Additionally, once you are on the keyboard, you expect that pressing ENTER corresponds to pressing the "Next" button, which doesn't happen. Same for the "Connect" button once you are on the next page. A double click on a selection item (such as "How will you connect to the blob container?") in a wizard should also move to the next page, which again doesn't happen. It would appear that a generic review for dialog boxes adhering to common Windows UI behaviours is needed.

fabiolavMS avatar Jul 24 '23 23:07 fabiolavMS

This seems to be true for almost all of our input elements. Can we figure out why there isn't a context menu w/copy & paste is happening and understand what it would take to fix this?

MRayermannMSFT avatar Sep 29 '23 17:09 MRayermannMSFT

Inputs by default in Electron do not have any context menus. The context menus would have to be created and attached to each input in the app to enable this functionality. The cost of doing so can be mitigated somewhat by the use of components.

Based on the size of the work here, I don't think we can make this into 1.33.0.

craxal avatar Jan 11 '24 19:01 craxal