Complete responsive and accessible workbench chrome

Cerrado
#44 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Ya se ha fusionado un pull request relacionado.

  • #47 de @rororowyourboat — fusionado

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
react, typescript

Línea de trabajo

Read the agreed 2026-11-16 product-design brief and inspect the preceding stages in issues #41, #42 and #43, plus the existing workbench layout and EditorTour. Start by mapping the listed layout, focus, accessibility and preservation acceptance checks to the relevant components and tests. Done means all breakpoint, interaction, preservation and accessibility checks are covered, the named documentation is updated, and targeted screen-reader coverage is recorded accurately.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Design stage 4 of 4

Integrate and verify the preceding toolbar, Model header and navigation stages against the agreed 2026-11-16 product-design brief. Each preceding stage still needs its own focused tests; this is the final cross-workbench pass.

Scope

  • Apply existing tokens to pane-local headers, arrangement controls and rail. Use actual pane/container width for wrapping rather than viewport width alone.
  • Retain horizontal Split at desktop, vertical Split below 900px, fresh narrow Inspector defaults and mutually exclusive Explorer/Inspector below 600px.
  • Keep Apply/Discard visible and labeled in narrow panes; primary navigation and mode switching must not disappear into secondary overflow on wide screens.
  • Distinguish Projects from Workspace layout icons. Treat model-kind icons as decorative context, retaining visible kind/type labels.
  • Finish obsolete toolbar-alignment/CSS cleanup only after replacements are integrated.
  • Update EditorTour selectors/labels, README, design-system and workbench-layout documentation.

Acceptance

  • Test 1440/1200, 900–1199, 600–899 and <600px layouts, including a wide window with narrow editor panes and transitions back to desktop.
  • No clipped critical controls; representation and arrangement remain independently obvious and operable.
  • Layout preferences retain sysml-workbench-layout-v1 compatibility. Collapse/restore and divider resize preserve drafts/history, selection, camera and saved geometry without automatic refit.
  • Hidden panes remain mounted/inert; focus transfers to visible reopen controls and returns correctly.
  • Test keyboard operation, selected vs focused state, forced colors and reduced motion. Perform and record targeted screen-reader checks; distinguish observed coverage from a comprehensive accessibility claim.
  • Preserve separate source draft undo vs accepted transaction history; navigation/layout must not mutate bundle data, semantic revision or project dirtiness.
  • Run relevant toolbar, panels, source-editor, diagnostics, model-tree, requirements/representation and preservation workflows; inspect light/dark desktop/narrow snapshots.
  • Retain explicit source-navigation guards and the Fit/100% overview-detail camera path from #38.

Related requirement: #31; inspection behavior also relates to #33. No new breakpoints without evidence, overlay Explorer redesign, shortcuts conflicting with CodeMirror, docking migration, semantic engine changes or portable-format changes.

Implementation order

Depends on #41, #42, #43. Keep this stage reviewable independently and preserve the preceding stages' acceptance checks.

Lenguaje dominante
TypeScript
Estrellas
2
Forks
0
Merge medio
13 h 40 min
PR fusionados (30 d)
17

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de Open-MBEE/sysml_view_editor

Todos los issues de Open-MBEE/sysml_view_editor

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.