fix(mantine, table): fix a few bugs when table is disabled by fieldset

[agong-coveo]

Proposed Changes

This PR tackles a few bugs that arise when a Table component is wrapped inside a fieldset. Essentially:

• If a table's rows contain checkboxes, despite being disabled, the checkboxes are still toggable when a user clicks on the row itself:

Bug.B.mov

• Also, after the changes made in this PR in Mantine, when bumping the mantine dependecies to the latest, the collapsible buttons are now disabled and its content becomes inaccessible. This is a bug since we still want users to be able to access the collapsed content.

The changes made to fix the bugs are the following:

• Modified the onClick method of the rows to take into account if its checkbox is disabled or not. If it is, then onClick is undefined;
• Modified the disabled style of the collapsible button to be clickable and to look enabled.

NOTE: Currently, there is also a bug with the Pagination and the PerPage component that is in a Table's footer. More precisely, these components are disabled and unclickable. This is an issue because users should still be able to view the items inside a table and be able to manipulate these components. This task was created to tackle it.

Potential Breaking Changes

None

Acceptance Criteria

• The proposed changes are covered by unit tests
• The potential breaking changes are clearly identified
• README.md is adjusted to reflect the proposed changes (if relevant)

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues found.

Scanned Manifest Files

[github-actions]

✔️ Live demo of your latest successful build available here.

[gdostie]

Row selection should still be enabled even when inside a disabled fieldset in some cases. Some row actions are still valid even in read-only mode.

For example, we often have a table row action that opens another panel to view the details of the resource represented by the row. Even if the table is disabled you still want to be able to view the resource's details.

[agong-coveo]

I see! From the examples in tanstack, I seem to have understood that row selection was for selecting and toggling the checkboxes associated to a row.

I'm not sure I understand the example completely. Are these details hidden inside a collapsible? Something like in the Sources panel?

If that's the case, if I'm not mistaken, this content becomes visible only when the user clicks on the arrow button and not on the row itself. The change here shouldn't affect access to the resource's details.

[gdostie]

You have an example of what I am referring to in your screenshot. In the table actions, we can see "Rescan", "Edit", "Activity", "... More". Those buttons still need to be activated even inside a disabled fieldset. Granted, not all of them, but the "Activity" one does, and the "... More" as well. The predicate filter and the text search filter too still need to be functional.

[gdostie]

Another concern of mine is sorting, what happens if you want to sort a table that is inside a disabled fieldset. Tables are more often than not presentational components rather than form control.

[agong-coveo]

Another concern of mine is sorting, what happens if you want to sort a table that is inside a disabled fieldset. Tables are more often than not presentational components rather than form control.

I absolutely agree with the fact that tables are more often presentational, which is why I think that everything should remain visible to the user even when it is disabled. When testing the component with a fieldset, I tried to make sure that despite being disabled, all items and content of the table are accessible. The sorting in this case isn't affected, and users can still sort a table without any issue even when it is disabled. Users are also able to access collapsed content and double clicking on a row is enabled as well. However, pagination right now still remains a problem, and a task has been created for this issue.

[agong-coveo]

Closed because the description of the task has changed.