fix(front): allow selection in readonly field display widgets

https://sonarly.com/issue/41520?type=bug Readonly/display-mode field values are wrapped in containers with Fix: Implemented a targeted CSS fix on the exact inline-cell wrappers in the affected render path so readonly/display-mode values are selectable again. Changes made: - `RecordInlineCellContainer.tsx`: changed `user-select` on `StyledInlineCellBaseContainer` from unconditional `none` to `readonly ? 'text' : 'none'`. - `FieldWidgetInlineCellContainer.tsx`: same conditional `user-select` update. - `RecordInlineCellHoveredPortalContent.tsx`: same conditional `user-select` update for hovered portal content wrapper. Why this fix: - It removes selection blocking specifically for readonly displays (the impacted user flow), while preserving the original non-selectable behavior for editable inline cells to avoid regressions in edit interaction UX. Authored by Sonarly by autonomous analysis (run 47342).
2026-05-29 13:36:21 +00:00
3 changed files with 3 additions and 3 deletions
@@ -61,7 +61,7 @@ const StyledInlineCellBaseContainer = styled.div<{ readonly: boolean }>`
  display: flex;
  gap: ${themeCssVariables.spacing[1]};
  height: fit-content;
-  user-select: none;
+  user-select: ${({ readonly }) => (readonly ? 'text' : 'none')};
  width: 100%;
 `;

@@ -21,7 +21,7 @@ const StyledInlineCellBaseContainer = styled.div<{ readonly: boolean }>`
  display: flex;
  gap: ${themeCssVariables.spacing[1]};
  height: fit-content;
-  user-select: none;
+  user-select: ${({ readonly }) => (readonly ? 'text' : 'none')};
  width: 100%;
 `;

@@ -21,7 +21,7 @@ const StyledInlineCellBaseContainer = styled.div<{ readonly: boolean }>`
  display: flex;
  gap: ${themeCssVariables.spacing[1]};
  height: fit-content;
-  user-select: none;
+  user-select: ${({ readonly }) => (readonly ? 'text' : 'none')};
  width: 100%;
 `;