Document stock visual decisions and operational UI examples

This commit is contained in:
mchus committed 2026-10-03 09:15:31 +03:00
1 parent 714447aa06
commit 08ff987edb
14 files changed
+532 -7

No files matched your search

@@ -15,3 +15,8 @@ Pattern-specific contracts should only define additions or exceptions.
Visual styling (colors, typography, surfaces) comes from `../web-visual-baseline/`.
The behavior/layout contract is `contract.md`.
For the dense parent/child variant, sticky scrolling surface, active filters and change-history
rows, see the [operational component sheet](../web-visual-baseline/assets/operations.html)
and [integration recipes](../web-visual-baseline/recipes.md). The extension deliberately keeps
horizontal scrolling; a sticky header is not a reason to clip columns.
+35 -1
View File
@@ -1,6 +1,6 @@
# Contract: Table Management (Shared)
Version: 1.1
Version: 1.2
## Scope
@@ -87,6 +87,40 @@ Canonical mapping:
- Server-side filtering only — do not filter an already-loaded JS array client-side unless the full
dataset is guaranteed small (< 500 rows) and never grows.
- Filter inputs debounce text input (300–500 ms) before triggering a server request.
- A shared collapsible filter panel may show the active-filter count and result count while
closed. Mark active fields inside it; collapsing it does not clear filters. Own URL state,
debounce and reset behavior in one shared module, with page-specific field declarations.
- Filter popups follow `controls-selection` placement rules, including in Gantt views;
raising z-index alone does not solve ancestor clipping or viewport overflow.
## Dense and Hierarchical Tables
- An operator-table density override may use `3px 14px` cell padding and middle alignment;
subordinate rows may use `1px` vertical padding and `18px` line height. Scope the override
to dense tables rather than changing key-value detail tables.
- Keep parents visually stronger than children. Indent children and align their columns;
omit redundant repeated parent fields. Expand only when there is meaningful detail.
- Expansion and editing are different actions. Use a keyboard-operable expand button with
`aria-expanded`; clicking a row action must not also toggle expansion.
- Sticky headers may use `border-collapse: separate; border-spacing: 0` to avoid collapsed
border rendering artifacts. Choose the scrolling owner explicitly. For a bounded table,
stick headers inside its scroll container and preserve horizontal scrolling.
Do not substitute `overflow-x: clip` for access to wide columns.
- Sorting uses one shared state cycle: ascending, descending, original order. Show the
direction and expose `aria-sort` on the header; use a button for keyboard activation.
Keep child groups attached to their parents. With server pagination, sort the query on
the server rather than just the loaded page.
## Change History Tables
- Use a dense event row with timestamp, actor, object and action, and expand multi-field
changes into labeled Before/After columns. Show a single meaningful change inline.
- A creation has an after value; a deletion has a before value. Do not render a misleading
empty-to-value arrow when there is no comparison.
- Combine a line item's name and quantity when they describe one change. Exclude technical
bookkeeping from the presentation, without deleting it from the underlying audit record.
- Event timestamps retain date/time precision. Formatting business dates as weeks must not
erase exact-date changes from the source audit data.
## Pagination Rules