fix(models): normalize mobile tab spacing and stabilize Combos layout - #3333
fix(models): normalize mobile tab spacing and stabilize Combos layout#3333blackjune67 wants to merge 6 commits into
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Team Run ID: 📒 Files selected for processing (4)
Included review availability: Your plan provides up to 10 included reviews per hour; 9 remain after this review. 📝 WalkthroughWalkthroughThe change updates Models workspace CSS selectors and fallback rules. Catalog, routing, and compatibility tabs retain 1200px widths in visible and shell-free states. Combos receives desktop and mobile spacing rules. A Bun test validates the resulting layout declarations. ChangesModels workspace layout
Estimated code review effort: 3 (Moderate) | ~20 minutes Merge Risk: ⚪ Minimal · up to This change standardizes Models-tab widths and Combos fallback spacing across desktop and mobile layouts. No current merge-blocking risk remains. Suggested reviewers: 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Full details: Title checkExplanation The title accurately summarizes the main changes: it identifies the Models tab scope, mobile spacing normalization, and Combos layout stabilization. It is concise and specific enough for the change set. Full details: Docstring CoverageExplanation Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 1 functions across 1 files. (3 skipped: 3 unsupported.)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
✅ Deterministic PR hygiene checks passed. |
✅ READY
Review readiness checklist
✅ 4/4 boxes ticked. This pull request is already Ready for Review. Hygiene✅ Deterministic PR hygiene checks passed. |
리뷰 · 우선순위 54 / 80이 PR은 Models 화면에서 탭을 왔다 갔다 할 때 가로 폭과 Combos 탭의 여백이 흔들리던 GUI 버그를 고친다. 지금 라인 styles-compatibility-matrix.css - 메인테이너의 판단이 필요한 지점
너의 추천 이 댓글은 grok-bot이 작성했습니다 |
CI was right and my earlier read of it was wrong. #3333 predates #3367, so taking gui/src/styles.css wholesale from the PR head silently reverted the newer Logs fix: .logs-table tbody td { overflow: hidden }, the .log-reasoning-cell wrap rule, and the .log-detail-btn wrapping that #3367 added on top. tests/logs-table-overflow.test.ts caught exactly that. This is the hazard in carrying a whole file rather than a diff, and it is why the guard test earned its keep.
Carried from #3333 onto current dev. Independent of the other carried fixes, so it ships as its own PR rather than a stack layer. The Models page keeps its panels mounted and toggles hidden, so width rules written against panel CONTENTS behaved differently depending on what had loaded and what had been visited: the catalog column gated on .models-workspace-shell, which is absent during the loading skeleton and after a cold failure, so the tab rendered at 980px and snapped to 1200px once data arrived. Routing had no rule at all and fell back to 980px. Scoping to the visible panel id fixes both and cannot leak to another tab. Combos separately renders its loading and error states without the workspace shell, so full-bleed styling stretched a lone notice edge to edge. That is now limited to the actual workspace. The dashboard page-tabs guard located its target with a bare indexOf(".page-tabs {"), which matches any rule whose selector merely ENDS in that string — including the scoped Combos rule this adds above it. Anchoring the search to a line-start rule fixes the guard without weakening it. Rebuilt from the PR's own diff rather than its files: the first attempt copied gui/src/styles.css wholesale and silently reverted both the Logs clipping fix (#3367) and the sidebar footer rework (#3382). Co-authored-by: hajune <june@smartix.co.kr>
…#3386) Carried from #3333 onto current dev. Independent of the other carried fixes, so it ships as its own PR rather than a stack layer. The Models page keeps its panels mounted and toggles hidden, so width rules written against panel CONTENTS behaved differently depending on what had loaded and what had been visited: the catalog column gated on .models-workspace-shell, which is absent during the loading skeleton and after a cold failure, so the tab rendered at 980px and snapped to 1200px once data arrived. Routing had no rule at all and fell back to 980px. Scoping to the visible panel id fixes both and cannot leak to another tab. Combos separately renders its loading and error states without the workspace shell, so full-bleed styling stretched a lone notice edge to edge. That is now limited to the actual workspace. The dashboard page-tabs guard located its target with a bare indexOf(".page-tabs {"), which matches any rule whose selector merely ENDS in that string — including the scoped Combos rule this adds above it. Anchoring the search to a line-start rule fixes the guard without weakening it. Rebuilt from the PR's own diff rather than its files: the first attempt copied gui/src/styles.css wholesale and silently reverted both the Logs clipping fix (#3367) and the sidebar footer rework (#3382). Co-authored-by: jun <jun@lidge.dev> Co-authored-by: hajune <june@smartix.co.kr>
|
Landed on dev as #3386 (a333811), carried onto current dev with your Co-authored-by trailer. Note for anyone carrying this next time: the first attempt copied gui/src/styles.css wholesale and silently reverted the Logs clipping fix (#3367) and the sidebar footer rework (#3382). The merged version applies your diff instead. |
Summary
Verification
bun x tsc --noEmitpassed.cd gui && bun run lintpassed.cd gui && bun test tests/models-tab-layout.test.tspassed with 18 assertions.Before
After
Checklist
Review readiness checklist
This PR stays in draft until every box below is ticked. Tick all four boxes once the requirements are met:
All CI tests are green on my local testing.
I pushed my PR to the latest dev commit.
I resolved all correct Codex and CodeRabbit findings.
My PR is ready for review.
Summary by CodeRabbit
Bug Fixes
Tests