Improve grid multiselect with ctrl/shift keys

[vaadin-bot]

Originally by plel

---

It would be helpful if the multiselect feature of the new Grid component could be improved. Selecting multiple entries must be done by clicking on each row's checkbox. If one wants to select a batch of e.g. 50 rows, 50 clicks are necessary.

Similar to ticket #3520 for the old table component, using shift to select all rows between two rows would be a major improvement.

It would also help if one could click anywhere in a row to select it. Pressing ctrl key should select the row under the cursor in addition to other selected rows. Clicking without the ctrl key should unselect other rows.

---

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

[vaadin-bot]

Originally by @jdahlstrom

---

Agreed. Note, though, that you can drag in the selection column to select many rows with a single gesture.

[vaadin-bot]

Originally by jonas.hahn

---

CTRL selection can be added by using the gridextensionpack

https://vaadin.com/directory#!addon/gridextensionpack-add-on

[ssindelar]

The missing functionality is a step backwards from Table.

Shift/Ctrl + Klick Selection is the standard for decades on PCs. The selection column works well with touch devices but it is PC users hard to explain why they can't use the standard methods for selection.

[tsuoanttila]

For now this is still not available in the framework core, but all old table selection modes are available for the Grid in the before mentioned GridExtensionPack.

[stale[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!