framework icon indicating copy to clipboard operation
framework copied to clipboard

Drag selection of Table rows

Open vaadin-bot opened this issue 14 years ago • 3 comments

Originally by @Artur-


Pressing mousedown and dragging down should select multiple rows in the Table (if multiselect is enabled). Dragging overrides this behavior so if Table is a drag source a mousedown + drag will start a drag operation and not select multiple rows.


Imported from https://dev.vaadin.com/ issue #4520

vaadin-bot avatar Apr 12 '10 08:04 vaadin-bot

Originally by @jouni


Dragging overrides this behavior so if Table is a drag source a mousedown + drag will start a drag operation and not select multiple rows. Drag source doesn't have to prevent drag-selection. See Apple Mail.app for instance. The drag'n'drop action is performed with a slight delay (click-hold-drag starts the drag'n'drop).

vaadin-bot avatar Apr 12 '10 09:04 vaadin-bot

Hello there!

It looks like this issue hasn't progressed lately. There are so many issues that we just can't deal them all within a reasonable timeframe.

There are a couple of things you could help to get things rolling on this issue (this is an automated message, so expect that some of these are already in use):

  • Check if the issue is still valid for the latest version. There are dozens of duplicates in our issue tracker, so it is possible that the issue is already tackled. If it appears to be fixed, close the issue, otherwise report to the issue that it is still valid.
  • Provide more details how to reproduce the issue.
  • Explain why it is important to get this issue fixed and politely draw others attention to it e.g. via the forum or social media.
  • Add a reduced test case about the issue, so it is easier for somebody to start working on a solution.
  • Try fixing the issue yourself and create a pull request that contains the test case and/or a fix for it. Handling the pull requests is the top priority for the core team.
  • If the issue is clearly a bug, use the Warranty in your Vaadin subscription to raise its priority.

Thanks again for your contributions! Even though we haven't been able to get this issue fixed, we hope you to report your findings and enhancement ideas in the future too!

stale[bot] avatar Mar 21 '18 03:03 stale[bot]

Hello there!

We are sorry that this issue hasn't progressed lately. We are prioritizing issues by severity and the number of customers we expect are experiencing this and haven't gotten around to fix this issue yet.

There are a couple of things you could help to get things rolling on this issue (this is an automated message, so expect that some of these are already in use):

  • Check if the issue is still valid for the latest version. There are dozens of duplicates in our issue tracker, so it is possible that the issue is already tackled. If it appears to be fixed, close the issue, otherwise report to the issue that it is still valid.
  • Provide more details how to reproduce the issue.
  • Explain why it is important to get this issue fixed and politely draw others attention to it e.g. via the forum or social media.
  • Add a reduced test case about the issue, so it is easier for somebody to start working on a solution.
  • Try fixing the issue yourself and create a pull request that contains the test case and/or a fix for it. Handling the pull requests is the top priority for the core team.
  • If the issue is clearly a bug, use the Warranty in your Vaadin subscription to raise its priority.

Thanks again for your contributions! Even though we haven't been able to get this issue fixed, we hope you to report your findings and enhancement ideas in the future too!

stale[bot] avatar Dec 19 '20 08:12 stale[bot]