If I double-click a row in the UI, it should still be selected, rather than the first click selecting it and the second click unselecting it. (You can still unselect a row with cmd+click.) In particular, it's confusing for linked tables, since you wind triggering the links based on an unselected row.
It'd also be more consistent with the multiple-row-selection experience — if you click and drag to select a handful of rows, and then click on one of them, it updates the selection to be just the one row you clicked on (rather than unselecting that row). And if click and drag to select select a handful of rows, and then click and drag again on the same set of rows, you wind up with all of them selected instead of unselected.
(It's also how the legacy swing UI works).
If I double-click a row in the UI, it should still be selected, rather than the first click selecting it and the second click unselecting it. (You can still unselect a row with cmd+click.) In particular, it's confusing for linked tables, since you wind triggering the links based on an unselected row.
It'd also be more consistent with the multiple-row-selection experience — if you click and drag to select a handful of rows, and then click on one of them, it updates the selection to be just the one row you clicked on (rather than unselecting that row). And if click and drag to select select a handful of rows, and then click and drag again on the same set of rows, you wind up with all of them selected instead of unselected.
(It's also how the legacy swing UI works).