Improve available diagram space and panel discoverability at narrow widths

未关闭
#31 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
react, typescript

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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.

主要语言
TypeScript
星标
2
派生
0
平均合并
13 小时 40 分钟
30 天内合并 PR
17

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

Open-MBEE/sysml_view_editor 的其他 Issue

查看 Open-MBEE/sysml_view_editor 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。