Improve available diagram space and panel discoverability at narrow widths

Abierto
#31 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

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

Línea de trabajo

Start with the linked WP26 feedback report, especially Suggestion 10, and inspect the editor at narrow widths using the example model files at the reported revision. Reproduce the layout and check how source and diagram modes, panel collapse and restore, drafts, keyboard focus, and light and dark layouts behave. Done means responsive defaults and discoverable restore controls are established, drafts and layout preferences are preserved, and the listed layouts and accessibility behaviors are covered.

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

Descripción

enhancement

Source and status

WP26 feedback report — Suggestion 10; section 2 item 10. Session dated 2026-11-10, using the hosted editor as served that day; deployed commit was not identified. The report does not establish current develop or current deployment behavior.

Reported by Zargham in WP26; not independently reproduced by maintainers.

Problem

At approximately 800px, Explorer, source and diagram competed for space and reduced the diagram to a thumbnail.

Reproduction / requested workflow

  1. Open a representative multi-file project at 800px and phone widths.
  2. Exercise source/diagram modes and panel collapse/restore.
  3. Return to desktop and inspect preserved preferences and drafts.

Acceptance / investigation criteria

  • Establish intentional responsive defaults and discoverable restore controls.
  • Keep a usable primary pane while preserving drafts and user-selected layout preferences.
  • Cover keyboard access, focus return and desktop/narrow light/dark layouts.

Evidence

Model files at the reported revision.

Preserve unapplied drafts and the last valid model. Record exact engine/build identity and distinguish a reported observation from a newly reproduced result.

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.