Skip to content

ui: follow-ups for the panel shell, popup and accessibility #370

Open

Description

@erkamyaman

Items still open from the audit issue #353. The fixed items landed in #364; this issue tracks what is left. Each item says why it was not part of that fix.

From #353 (panel shell, popup and accessibility)

Open:

  • Shell improvement: programmatic buildReport(): New public package API.
  • Shell improvement: remember scroll/selection per tab: Touches every page's state; not small or local.
  • Shell improvement: minimized pill launcher with counts: New UI feature that needs a design decision.
  • Panel: Search fields differ from page to page (Low): Needs a new shared component across six or more pages and a choice between 'Filter' and 'Find'.
  • Panel: Route tree has no tree semantics (Low): A treegrid with expand/collapse keys is a larger restructure of route-current.ts.
  • Panel: Filtered lists tracked by $index (Low): The listed rows have no selection and, except forms-report, no focusable content. cd-recording uses $index on purpose for repeated names (duplicate-track-keys test). No unique stable key exists without adding a keying helper.
  • Panel: Hex colors in the Analog view (Low): Moving about ten colour pairs into the palette and the contrast test is a palette change across several files, not a small fix.
  • Panel improvement: shared <app-state> component and spec: Cross-page refactor.
  • Panel improvement: spec checking search-field/roving usage: Depends on the search-field component, which was skipped.
  • Panel improvement: resizable panes with splitter: New feature across several pages; needs a design decision.
  • Panel improvement: pause live updates / auto-scroll toggles: New feature across three pages; needs a product decision.
  • Panel improvement: sortable column headers with aria-sort: New feature across two tables; needs a design decision.
  • Panel improvement: saved filter chips per view: New feature; needs a product decision.
  • Panel improvement: run test:axe on loading/error/no-match states: Changes the static report build and the axe harness; not local.

Tracked elsewhere

These items from the audit are not listed above because another issue already tracks them:

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething is broken or shows wrong datafeatureA feature request or a pull request that adds one

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions