Skip to content

fix(ui): ensure raw config textarea is visible and scrollable#94205

Closed
lsr911 wants to merge 1 commit into
openclaw:mainfrom
lsr911:fix/issue-94202-Bug-UI-glitch-config-is-no
Closed

fix(ui): ensure raw config textarea is visible and scrollable#94205
lsr911 wants to merge 1 commit into
openclaw:mainfrom
lsr911:fix/issue-94202-Bug-UI-glitch-config-is-no

Conversation

@lsr911

@lsr911 lsr911 commented Jun 17, 2026

Copy link
Copy Markdown
Contributor

Summary

Fixes #94202 — UI glitch: Raw config JSON not visible in settings view.

Root Cause

The .config-layout and .config-main containers use overflow: clip which prevents content from being scrolled into view. The raw config textarea had min-height: 500px but no flex sizing, so when the JSON content was larger than the viewport, it overflowed the clipped container and became invisible.

Fix

ui/src/styles/config.css — +10 lines

  • Add flex: 1; display: flex; flex-direction: column; min-height: 0 to .config-raw-field
  • Add flex: 1; overflow-y: auto; resize: vertical to .config-raw-field textarea

The textarea now fills the available vertical space and scrolls independently, ensuring the JSON content is always accessible regardless of length.

@lsr911 @claude
fix(ui): ensure raw config textarea is visible and scrollable
02165b0 
The config-layout and config-main containers use overflow:clip
which prevents the raw config textarea from being visible when
the JSON content is large. The textarea had min-height:500px
but no flex sizing, so it could overflow the clipped container
and become invisible.

Add flex layout to .config-raw-field wrapper and textarea so
the textarea fills available space and scrolls independently.

Closes openclaw#94202

Co-Authored-By: Claude <[email protected]>
@openclaw-barnacle openclaw-barnacle Bot added app: web-ui App: web-ui size: XS triage: needs-real-behavior-proof Candidate: external PR needs after-fix proof from a real setup. labels Jun 17, 2026
@NianJiuZst

NianJiuZst commented Jun 17, 2026

Copy link
Copy Markdown
Contributor

Should be closed.This issue has been resolved in v2026.6.8.

@clawsweeper

clawsweeper Bot commented Jun 17, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

ClawSweeper review: did not complete due to Codex infrastructure failure. Reviewed June 17, 2026, 12:12 PM ET / 16:12 UTC.

Summary
Review failed before ClawSweeper could summarize the requested change.

PR surface: Source +10. Total +10 across 1 file.

Reproducibility: unclear. The review failed before ClawSweeper could establish a reproduction path.

Review metrics: none identified.

Merge readiness
Not assessed.
Failure reason: invalid structured output.

This is a ClawSweeper/Codex infrastructure failure, not a PR readiness or patch-quality verdict.
Keep any merge decision on the normal maintainer review path until ClawSweeper can complete a fresh review.

Risk before merge

  • [P1] No close action taken because the review did not complete.

Maintainer options:

  1. Decide the mitigation before merge
    Retry the Codex review after fixing the execution failure.
  2. Pause or close
    Do not merge this PR until maintainers decide whether the risk is worth taking.

Next step before merge

  • Review did not complete, so no work-lane recommendation was made.
Review details

Best possible solution:

Retry the Codex review after fixing the execution failure.

Do we have a high-confidence way to reproduce the issue?

Unclear. The review failed before ClawSweeper could establish a reproduction path.

Is this the best way to solve the issue?

Unclear. Retry the review first so ClawSweeper can evaluate the actual issue and fix direction.

AGENTS.md: unclear because the file could not be read completely.

Codex review notes: model internal, reasoning high; reviewed against 59fb68588435.

Evidence reviewed

PR surface:

Source +10. Total +10 across 1 file.

View PR surface stats
Area Files Added Removed Net
Source 1 10 0 +10
Tests 0 0 0 0
Docs 0 0 0 0
Config 0 0 0 0
Generated 0 0 0 0
Other 0 0 0 0
Total 1 10 0 +10

What I checked:

  • failure reason: invalid structured output.
  • codex failure detail: Codex review failed for this PR with exit 0 and wrote invalid JSON or schema-invalid output to /home/runner/work/clawsweeper/clawsweeper/artifacts/event/codex/94205.json: decision.rootCauseCluster fixed_by_candidate requires a canonical pull request.
  • codex stderr: No stderr captured.
  • codex stdout: browser screenshot, recording, terminal output, logs, or linked artifact showing Settings > Raw with a long or sensitive config."],"bestSolution":"Fix the raw-config render/reveal behavior in config.ts with focused browser tests and redacted visual proof; keep CSS-only changes only if they are proven necessary for the long-text scroll case.","triagePriority":"P2","impactLabels":[],"mergeRiskLabels":[],"mergeRiskOptions":[],"reviewMetrics":[],"labelJustifications":[{"label":"P2","reason":"This is a normal-priority web UI bug fix attempt with limited blast radius, but it affects a user-visible Settings workflow."}],"itemCategory":"bug","reproductionStatus":"source_reproducible","reproductionConfidence":"high","requiresNewFeature":false,"requiresNewConfigOption":false,"requiresProductDecision":false,"reproductionAssessment":"Yes, at source level: current main sets rawRevealed to fal.

Likely related people:

  • unknown: Codex failed before it could trace repository history. (role: review did not complete; confidence: low)
How this review workflow works
  • ClawSweeper keeps one durable marker-backed review comment per issue or PR.
  • Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
  • A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
  • PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
  • Maintainers can also comment @clawsweeper review to request a fresh review only.
  • Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
  • Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
  • Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

@lsr911

lsr911 commented Jun 18, 2026

Copy link
Copy Markdown
Contributor Author

Closing to reduce active PR count (bot limit: 20). This PR needs real behavior/environment verification that automated tooling cannot provide. Will reopen if maintainers confirm it's actionable.

@lsr911 lsr911 closed this Jun 18, 2026
This was referenced Jun 18, 2026
Closed
Closed
Closed
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

app: web-ui App: web-ui size: XS triage: needs-real-behavior-proof Candidate: external PR needs after-fix proof from a real setup.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

[Bug]: UI glitch: config is not visible

2 participants

@lsr911 @NianJiuZst