You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Development Relevant Information:
I have a run-of-the-mill table with a paginator at the bottom. Importantly, I want the rows to have checkboxes, which puts a "check all" checkbox in the header. I've noticed that when the user clicks that checkbox, only the items in the current page are selected. There does not appear to be a way to handle/intercept that event. How should I do it?
I would like to be able to handle a "check all" event on a table component with a paginator. As it is now, only the current page's items are checked, and I'd like to at least ask the user if they want all items selected. (I'm thinking of GMail's warning when checking all...)
Steps To Reproduce:
Create a table with the row-checkbox property set and a paginator. Add enough items to have multiple pages. Check the "check all" checkbox in the header row. There doesn't appear to be a way to handle that event.
The text was updated successfully, but these errors were encountered:
Development Relevant Information:
I have a run-of-the-mill table with a paginator at the bottom. Importantly, I want the rows to have checkboxes, which puts a "check all" checkbox in the header. I've noticed that when the user clicks that checkbox, only the items in the current page are selected. There does not appear to be a way to handle/intercept that event. How should I do it?
Description:
I would like to be able to handle a "check all" event on a table component with a paginator. As it is now, only the current page's items are checked, and I'd like to at least ask the user if they want all items selected. (I'm thinking of GMail's warning when checking all...)
Steps To Reproduce:
Create a table with the row-checkbox property set and a paginator. Add enough items to have multiple pages. Check the "check all" checkbox in the header row. There doesn't appear to be a way to handle that event.
The text was updated successfully, but these errors were encountered: