ui5-webcomponents
ui5-webcomponents copied to clipboard
Table: add "Clear All" functionality
Feature Request Description
Add the multi-select variant "Clear All" to the table, as described here.
Additional Context
We're implementing a FilterBar component, there the filter dialog in list view should contain a multi-select table with the option to clear all entries. You can see this in the SAPUI5 demo. There you can click on filters and the initial view contains the table with clear-all "checkbox".
Priority
- [ ] Low
- [x] Medium
- [ ] High
- [ ] Very High
Stakeholder Info (if applicable)
- Organization: UI5 Web Components for React
Hello @SAP/ui5-webcomponents-topic-rl, Please take a look at this feature request.
Hello Colleagues,
In SAPUI5 that functionality is handled via "multiSelectMode" property - (Defines the multi-selection mode for the control. If this property is set to the Default value, the sap.m.Table control renders the Select All checkbox in the column header, otherwise the Deselect All icon is rendered. The Select All checkbox allows the user to select all the items in the control, and the Deselect All icon deselects the items. If the property is set to ClearAll, then selecting items via the selectAll method is not possible. See selectAll for more details. Note: This property must be used with the MultiSelect mode. If this property is set to ClearAll, then a selection of multiple items is still possible via the range selection feature except CTRL + A. Additionally, the CTRL + SHIFT + A key combination can be used for deselecting all the items. For details on the range selection, please see Keyboard Handling for Item Selection. Since: 1.93. Visibility: public Borrowed from: sap.m.ListBase)
Please, analyse whether it is possible to introduce such a functionality in ui5-table Web Component.
Thank you in advance!
Kind Regards, Niya
Hi @Lukas742
We are writing to inform you about an important development regarding our ui5-table component. After careful consideration and received feedback, we have decided to focus on re-implementing and improving the existing table component based on the gathered feature requests and requirements. Here are some details about this decision and how it may affect our ongoing development efforts.
The decision was made based on several factors, including scalability, performance, accessibility and the ability to meet future feature requirements. Our team has recognised the limitations of the current table component and after careful consideration, we concluded that it would be more effective to develop a new table component from scratch rather than invest more time in enhancing the current one.
While this decision allows us to provide a better user experience and meet evolving needs, I want to acknowledge that it may have some implications for the feature requests that have been made for the current ui5-table component. We understand that stakeholders have invested time and effort in suggesting improvements and new features. Rest assured that we value your input, and we will make every effort to take these feature requests into consideration during the development of the new ui5-table component.
However, it is important to note that the new table component may introduce backward incompatible changes. These changes may impact the way the current table component functions, including its API and visual representation. We understand that this may require adjustments and adaptations on your end. Our team will strive to provide documentation and guidance to facilitate a smooth transition to the new table component.
We are excited about the opportunities this transition will bring and the positive impact it will have on our product.
Should you have any questions or concerns regarding this transition or its implications, please don't hesitate to reach out.
Thank you for your understanding and continued support as we embark on this important transition. Unfortunately for now we are not able to provide concrete timelines but we are currently working on a first preview version of the new WebComponent which should already offer a first impression of the concepts behind. We have gathered the feature requests and we surely have them in mind while developing the new component.
Best Regards, Hristo