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
I have searched the issues of this repository and believe that this is not a duplicate.
What problem does this feature solve?
Current UI implementation of disabled checkbox for a-table is not super clear. It is a slightly greyed out version of the regular checkbox which at a glance isn't easy to notice. Disabling selection of a specific table row could mean multiple things; i.e row is locked. For this reason, if users could slot their own component to the checkbox on the a-table (or to the disabled checkbox/radio) it would allow for more options/custom visuals of the disabled checkbox.
This would also be helpful for slotting a tooltip to the disabled-checkbox for more information as to why a specific row is disabled.
What does the proposed API look like?
To slot a tooltip to an ant design table disabled checkbox:
<a-table>
<template slot="disabled-selection-box">
<a-tooltip>
<a-icon type="lock" />
<span slot="title">This row is locked because of a reason</span>
</a-tooltip>
</template>
</a-table>
The text was updated successfully, but these errors were encountered:
What problem does this feature solve?
Current UI implementation of disabled checkbox for
a-table
is not super clear. It is a slightly greyed out version of the regular checkbox which at a glance isn't easy to notice. Disabling selection of a specific table row could mean multiple things; i.e row is locked. For this reason, if users could slot their own component to the checkbox on thea-table
(or to thedisabled
checkbox/radio) it would allow for more options/custom visuals of the disabled checkbox.This would also be helpful for slotting a tooltip to the
disabled-checkbox
for more information as to why a specific row is disabled.What does the proposed API look like?
To slot a tooltip to an ant design table disabled checkbox:
The text was updated successfully, but these errors were encountered: