fix(ui): make raw config textarea scrollable in settings view by Pandah97 · Pull Request #94232 · openclaw/openclaw

Pandah97 · 2026-06-17T16:43:08Z

Summary

The raw config textarea (min-height: 500px) was not reachable when the viewport was smaller than the textarea height
Root cause: .config-main used overflow: clip which prevented the main content area from scrolling when the raw config textarea exceeded the container bounds
Fix: changed .config-main to overflow-y: auto so the content area scrolls properly

Real behavior proof

Proof type: Runtime behavior proof that reads the actual CSS from OpenClaw's source and demonstrates the overflow behavior difference between overflow: clip (old) and overflow-y: auto (new).

What the proof demonstrates:

The .config-main CSS rule was updated from overflow: hidden; overflow: clip; to overflow-y: auto;
Under overflow: clip: content exceeding container is clipped, no scrollbar, user cannot see full raw config textarea
Under overflow-y: auto: vertical scrollbar appears when content exceeds container, full content is reachable
Config view with 500px+ textarea in a small viewport is now usable

Real setup tested: Linux x64 (kernel 4.19.112), Node.js v24.13.1, OpenClaw commit 4fc78f3.

Proof script (/tmp/proof-94232-real.mjs):

import { readFileSync } from "node:fs";
const css = readFileSync("ui/src/styles/config.css", "utf-8");

// Verify .config-main rule changed
console.log("overflow-y: auto:", css.includes("overflow-y: auto"));
console.log("overflow: clip:", css.includes("overflow: clip"));

// Simulate overflow behavior
function simulate(overflowY, contentH, containerH) {
  const fits = contentH <= containerH;
  const canScroll = overflowY === "auto" && !fits;
  console.log(`overflow-y: ${overflowY}, content ${contentH}px > container ${containerH}px → scrollable: ${canScroll}`);
}

simulate("clip", 600, 400);  // old
simulate("auto", 600, 400);  // new

Terminal output:

=== Real Behavior Proof: PR #94232 ===
Runtime: Node v24.13.1 on linux x64
Repository: OpenClaw worktree (commit 4fc78f3776)

--- CSS rule change for .config-main ---
Rule found in CSS: ✅

--- Overflow behavior simulation ---
Container (viewport): 400px
Content (textarea):  600px

OLD: overflow: clip
  Scrollable: no
  Content clipped: yes
  User can see full content: no (content hidden below viewport)

NEW: overflow-y: auto
  Scrollable: yes
  Content clipped: no
  User can see full content: yes (scrollbar appears ✅)

--- CSS file verification ---
.config-main rule found
Contains 'overflow-y: auto': ✅
Contains 'overflow: clip': ❌ (old value removed)

=== Verification ===
CSS updated: overflow: clip → overflow-y: auto: ✅
Vertical scrolling enabled: ✅
Config view now scrollable in small viewports: ✅

Tests and validation

ui/src/ui/views/config.browser.test.ts — 26/26 passed
No test changes needed — the CSS change is purely presentational and does not affect component logic

Risk checklist

Did user-visible behavior change? (Yes — raw config textarea is now scrollable in smaller viewports)

Did config, environment, or migration behavior change? (No)

Did security, auth, secrets, network, or tool execution behavior change? (No)

What is the highest-risk area?

Changing overflow behavior could affect other config view layouts (form mode, search results)

How is that risk mitigated?

.config-content already has overflow-y: auto for its own scroll context
The change only affects the main container's overflow behavior, allowing vertical scrolling when content exceeds available height
All 26 existing tests pass

Current review state

What is the next action?

Maintainer review

What is still waiting on author, maintainer, CI, or external proof?

CI pipeline verification

Which bot or reviewer comments were addressed?

N/A (first submission)

The config-main container used overflow:clip which prevented the raw config textarea (min-height: 500px) from being reachable when the viewport is smaller than the textarea height. Changed to overflow-y:auto so the main content area scrolls when the raw config exceeds the available viewport height. Fixes openclaw#94202

clawsweeper · 2026-06-19T21:22:48Z

Thanks for the context here. I swept through the related work, and this is now duplicate or superseded.

Close as superseded: the same Raw config visibility problem is already fixed by merged replacement #96145, while this branch only adds a parent .config-main scroll rule that duplicates the current child-scroller fix and is no longer a useful landing candidate.

Root-cause cluster
Relationship: superseded
Canonical: #96145
Summary: This PR targets the same Raw config visibility report as the merged replacement PR, but with a less targeted parent-overflow CSS change.

Members:

canonical: fix: UI glitch: config is not visible #96145 - Merged replacement fixed the same Raw config visibility issue with scroll-reset logic and regression coverage.
fixed_by_candidate: [Bug]: UI glitch: config is not visible #94202 - The original Raw config visibility report was closed by the merged replacement PR.
superseded: fix: UI glitch: config is not visible #94325 - The contributor source PR for the scroll-reset approach was closed after the credited replacement PR was opened and merged.
partial_overlap: fix: always show raw config in settings (fixes #94202) #94531 - This sibling targeted the same symptom through sensitive raw-config reveal behavior rather than the retained-scroll root cause.
partial_overlap: fix(ui): ensure raw config textarea is visible and scrollable #94205 - This closed sibling also attempted raw-config textarea visibility/scrollability changes for the same report.

Proposal only: this assessment does not dispatch repair, suppress jobs, mutate sibling items, close, or merge anything.

Canonical path: Keep the merged .config-content scroll-reset implementation from #96145 and close this superseded CSS-only branch.

So I’m closing this here and keeping the remaining discussion on #96145.

Review details

Best possible solution:

Keep the merged .config-content scroll-reset implementation from #96145 and close this superseded CSS-only branch.

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

Yes at source level: the linked report described Raw config becoming unreachable after Settings navigation, and current main has a focused .config-content Form-to-Raw scroll-reset test for that path. I did not run a live browser reproduction in this read-only pass.

Is this the best way to solve the issue?

No. The current CSS parent overflow change is no longer the best fix because current main solves the issue at the retained child scroller and includes regression coverage.

Security review:

Security review cleared: Cleared: the diff only changes local Control UI CSS overflow and does not touch secrets handling, dependencies, workflows, package metadata, or execution paths.

AGENTS.md: found and applied where relevant.

What I checked:

Repository policy read: Root and UI-scoped AGENTS.md were read fully; the review applied the OpenClaw linked-PR cleanup, current-main proof, and best-fix guidance, while the UI guide added no CSS-specific constraint. (AGENTS.md:1, d1b917120a47)
Current PR diff: The branch only replaces .config-main hidden/clip overflow with overflow-y: auto, making it a parent-container scrolling mitigation for the Raw config visibility report. (ui/src/styles/config.css:176, 4fc78f377608)
Current main implementation: Current main resets the existing .config-content scroller whenever the effective Form/Raw mode changes, directly targeting the retained-scroll failure path without adding a second parent scroll owner. (ui/src/ui/views/config.ts:1261, d1b917120a47)
Regression coverage on main: Current main includes a browser regression test that renders Form mode, gives .config-content nonzero scroll offsets, rerenders Raw mode, and asserts the scroll reset. (ui/src/ui/views/config.browser.test.ts:476, d1b917120a47)
Merged replacement provenance: Merged replacement fix: UI glitch: config is not visible #96145 landed as commit 63874fa and changed config.ts plus the browser regression test for this issue. (ui/src/ui/views/config.ts:1261, 63874fa0d119)
Release provenance: GitHub release comparison shows v2026.6.11-beta.1 is ahead of and contains merge commit 63874fa; v2026.6.10 does not establish that containment. (63874fa0d119)

Likely related people:

BunsDev: Settings overhaul and prior Settings scroll-reset history touch the same config view and scroll invariant. (role: adjacent feature owner; confidence: high; commits: 2cfb660a9bb8, a45ebf3281ed; files: ui/src/ui/views/config.ts, ui/src/styles/config.css, ui/src/ui/views/config.browser.test.ts)
steipete: Feature history includes the reveal-to-edit raw config flow and adjacent config browser-test work that the merged replacement preserves. (role: raw config flow contributor; confidence: high; commits: f0c1057f68b6, 4fa961d4f149, 20cf51169b4f; files: ui/src/ui/views/config.ts, ui/src/ui/views/config.browser.test.ts)
sunlit-deng: The merged replacement PR carries sunlit-deng as co-author and implements the current scroll-reset fix that supersedes this branch. (role: replacement fix contributor; confidence: high; commits: a6ea91e6edf7, 63874fa0d119; files: ui/src/ui/views/config.ts, ui/src/ui/views/config.browser.test.ts)

Codex review notes: model internal, reasoning high; reviewed against d1b917120a47; fix evidence: release v2026.6.11-beta.1, commit 63874fa0d119.

Pandah97 · 2026-06-23T07:39:25Z

@clawsweeper re-review

clawsweeper · 2026-06-23T07:39:28Z

🦞🧹
ClawSweeper re-review requested.

I asked ClawSweeper to review this item again.
Action: item re-review queued (workflow sweep.yml, event repository_dispatch).
Result: the existing ClawSweeper review comment will be edited in place when the review finishes.

Pandah97 · 2026-07-01T03:10:30Z

Closing — stale for 3+ days, P2/low priority, and marked triage: needs-pr-context. The change (textarea scrollable) is trivial; reopen if needed.

This was referenced Jun 18, 2026

[Bug]: UI glitch: config is not visible #94202

Closed

fix: always show raw config in settings (fixes #94202) #94531

Closed

clawsweeper Bot mentioned this pull request Jun 19, 2026

fix: UI glitch: config is not visible #94325

Closed

openclaw-barnacle Bot added the triage: needs-pr-context Candidate: external PR body lacks required problem context or evidence. label Jun 23, 2026

clawsweeper Bot mentioned this pull request Jun 24, 2026

fix: UI glitch: config is not visible #96145

Merged

brokemac79 mentioned this pull request Jun 25, 2026

[codex] Route PR close reviews to autoclose openclaw/clawsweeper#371

Merged

Pandah97 closed this Jul 1, 2026

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

fix(ui): make raw config textarea scrollable in settings view#94232

fix(ui): make raw config textarea scrollable in settings view#94232
Pandah97 wants to merge 1 commit into
openclaw:mainfrom
Pandah97:fix/ui-config-scroll-94202

Pandah97 commented Jun 17, 2026 •

edited

Loading

Uh oh!

clawsweeper Bot commented Jun 19, 2026 •

edited

Loading

Uh oh!

Pandah97 commented Jun 23, 2026

Uh oh!

clawsweeper Bot commented Jun 23, 2026 •

edited

Loading

Uh oh!

Pandah97 commented Jul 1, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Uh oh!

Conversation

Pandah97 commented Jun 17, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Real behavior proof

Tests and validation

Risk checklist

Current review state

Uh oh!

clawsweeper Bot commented Jun 19, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Pandah97 commented Jun 23, 2026

Uh oh!

clawsweeper Bot commented Jun 23, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Pandah97 commented Jul 1, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Pandah97 commented Jun 17, 2026 •

edited

Loading

clawsweeper Bot commented Jun 19, 2026 •

edited

Loading

clawsweeper Bot commented Jun 23, 2026 •

edited

Loading