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

[BUG] - Clicking checkboxes in a multiple selection mode <Table> component no longer causes that row to be selected #4252

Closed
Kismet333 opened this issue Dec 7, 2024 · 6 comments · Fixed by #4311 or #4298
Labels
📦 Scope : Components Related to the components 🐛 Type: Bug Something isn't working

Comments

@Kismet333
Copy link

Kismet333 commented Dec 7, 2024

NextUI Version

2.6.3

Describe the bug

I just upgraded my NextUI to version 2.6.3 and I found that clicking checkboxes in a multiple selection mode <Table> component no longer causes that row to be selected. The row still can be selected if its clicked anywhere else except the checkbox. This includes the main "select all" checkbox in the header of the table, it is no longer selectable.

Your Example Website or App

No response

Steps to Reproduce the Bug or Issue

  1. Create a <Table> component with its selectionMode='multiple'.
  2. Add at least 1 row.
  3. Attempt to click a row's checkbox.

Expected behavior

The row becomes selected.

Screenshots or Videos

No response

Operating System Version

Windows

Browser

Chrome

@wingkwong wingkwong added 🐛 Type: Bug Something isn't working 📦 Scope : Components Related to the components labels Dec 7, 2024
@gregmsanderson
Copy link

Noticed this too.

It can be seen on all the demos on the site e.g https://nextui.org/docs/components/table#multiple-row-selection

@Peterl561
Copy link
Contributor

Seems to be related to #4220.

@mayeenulislam
Copy link

Also need to check with #4145

@chintan-traitfit
Copy link

This is a high-priority bug that needs to be fixed, as it is preventing multiple table row selection.

@macci001
Copy link
Contributor

macci001 commented Dec 9, 2024

Sorry for the inconvenience caused. RCA for this issue is done and fix will be released soon.
PR to track the fix: #4274

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment