Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Right-clicking table entities for delete selects two rows #2107

Closed
cliffeby opened this issue Oct 17, 2019 · 14 comments
Closed

Right-clicking table entities for delete selects two rows #2107

cliffeby opened this issue Oct 17, 2019 · 14 comments
Assignees
Labels
👁️‍🗨️ theming Related to dynamic theming ⚙️ tables Related to table storage
Milestone

Comments

@cliffeby
Copy link

cliffeby commented Oct 17, 2019

Storage Explorer Version: 1.10.1
Build Number: 201990919.2
Platform/OS: Windows 10?
Architecture: x64?
Regression From: no

Bug Description

When you right click to delete a table row, the selected and the mouse located rowsare highlighted. Confirming the delete only removes the initially selected row as it should, but the warning message with two rows identified is misleading.

Steps to Reproduce

  1. Right click any row in a table and select delete

Expected Experience

highlight only one selected row or use a bold color for the selected row.

Actual Experience

Additional Context

@JasonYeMSFT
Copy link
Contributor

Could you please give more detailed steps to reproduce the bug?

@MRayermannMSFT MRayermannMSFT added the ❔ more info More information is needed from issue author to proceed label Oct 21, 2019
@cliffeby
Copy link
Author

Sorry had these details in html comments.

@cliffeby
Copy link
Author

cliffeby commented Oct 21, 2019 via email

@JasonYeMSFT
Copy link
Contributor

Could you please attach a screenshot or a recording showing the bug you are describing? We are having trouble reproducing this issue.

@cliffeby
Copy link
Author

cliffeby commented Nov 6, 2019 via email

@MRayermannMSFT
Copy link
Member

We don't see a screenshot. You need to paste it directly into your github comment. Attaching it to your email reply won't work.

@cliffeby
Copy link
Author

@MRayermannMSFT
Copy link
Member

Thanks. We understand the issue and will look into getting this fixed.

@MRayermannMSFT MRayermannMSFT modified the milestones: 1.13.0, 1.15.0 Dec 16, 2019
@craxal craxal changed the title Delete is highlighting two rows Right-clicking table entities for delete selects two rows Jul 24, 2020
@craxal craxal added ⚙️ tables Related to table storage ❗ P0 and removed ❔ more info More information is needed from issue author to proceed labels Jul 24, 2020
@craxal
Copy link
Contributor

craxal commented Jul 30, 2020

Unable to reproduce this issue on 1.14.2. When I try right-clicking an item different than the current selection, the current selection is set to that item as expected.

@cliffeby Can you reproduce on the latest version (1.14.2) of Storage Explorer?

@v-xianya Can you try reproducing this issue as well?

@cliffeby
Copy link
Author

ASE073020a
I still get the same behavior but less consistently. About half the time only one line is highlighted. When only one line is highlighted and then deleted, a new cell is highlighted at the top of the page. The jump and highlighting is disconcerting/unexpected. @craxal @v-xianya

@cliffeby
Copy link
Author

IMG_3752.zip

This is a video showing both issues.

@craxal
Copy link
Contributor

craxal commented Aug 3, 2020

@cliffeby The jump to the top of the page is by design. All of our editors do that.

As far as the double-selection is concerned, I finally got it to repro. I think I know what's happening. The Delete command, of course, opens a confirmation dialog before proceeding. There's often a (very) short delay between when the command is triggered and the dialog opens. During that delay, the editor can still respond to UI events. In this case, a few things are happening:

  • The table loses focus. This results in the selected row changing from dark blue to light blue.
  • The UI handles a mouseover at the current location of the cursor. This results in the row under the cursor also being colored light blue.
  • The editor UI is blocked as soon as the dialog opens, so the editor doesn't change any hover states.

It just so happens the colors we use for row hover color and row unfocused/selected states are the same color, which is probably where the confusion is coming from. In reality, only one item is selected. If you cancel the confirmation dialog, you should notice the UI update the row hover.

Two possible solutions:

  • We have a different style for row hover and row unfocused/selected states.
  • Indicate the number of entities that will be deleted in the confirmation dialog.

@jinglouMSFT @MRayermannMSFT @JasonYang-MSFT Thoughts?

@cliffeby
Copy link
Author

cliffeby commented Aug 4, 2020

@craxal @jinglouMSFT @MRayermannMSFT @JasonYang-MSFT

Regarding options, I'd prefer style/color difference as long as it's obvious which is going to be deleted.. For the second possible solution, if the confirmation dialog notes one row to be deleted and two are highlighted, which one is it?

Regarding standard editor behavior, I'm not sure why a jump to the top of the page is desired. Why would I want to go to the top of a page? Could you imagine that behavior in VSCode, Excel or Word?

@craxal craxal removed the ❗ P0 label Aug 4, 2020
@craxal craxal modified the milestones: 1.15.0, 1.16.0 Aug 6, 2020
@craxal
Copy link
Contributor

craxal commented Aug 27, 2020

@cliffeby We try to emulate behaviors observed in File Explorer on Windows or Finder on Mac. Both File Explorer and Finder move the selection to the next item when deleting, so that's something we can look into. If could please open a separate bug for that, we'd greatly appreciate it!

@craxal craxal added the 👁️‍🗨️ theming Related to dynamic theming label Aug 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
👁️‍🗨️ theming Related to dynamic theming ⚙️ tables Related to table storage
Projects
None yet
Development

No branches or pull requests

4 participants