feat(viewer): compact status and severity table icons
This commit is contained in:
@@ -0,0 +1,31 @@
|
||||
# Decision: Status Table Columns Use Icon-Only Presentation
|
||||
|
||||
**Date:** 2026-04-22
|
||||
**Status:** active
|
||||
|
||||
## Context
|
||||
|
||||
Dense hardware tables frequently repeat the same `status` values.
|
||||
|
||||
Showing a textual `status` header and textual badges in every row wastes horizontal space and reduces scan speed, especially in sensor subtables.
|
||||
|
||||
The viewer still needs to keep status meaning explicit and avoid relying on color alone.
|
||||
|
||||
## Decision
|
||||
|
||||
Table columns named `status` render as compact icon-only columns.
|
||||
|
||||
This includes:
|
||||
|
||||
- an empty visible header cell for the `status` column
|
||||
- a minimal-width table column sized for the pictogram
|
||||
- a glyph plus color to distinguish state
|
||||
- accessible labeling that preserves the raw status value without showing repeated text in the cell
|
||||
|
||||
Object sections may continue to show status as a regular field value.
|
||||
|
||||
## Consequences
|
||||
|
||||
- Table layouts gain more room for source fields such as `name`, `model`, and `location`.
|
||||
- Status meaning remains available to assistive technologies even when the visible cell is icon-only.
|
||||
- Future table UI work should keep `status` compact instead of reintroducing wide text badges by default.
|
||||
Reference in New Issue
Block a user