Bug: MCP advanced settings scroll failure, run log details overlap, timestamp rendered as {time}

[MrWoods1692]

Issue Report: Mosoo Cloud Platform UI/UX Defects (MCP Server Settings, Run Log Details, Timestamp Placeholder)

Cloud Platform MCP Server advanced settings cannot scroll, run log popup text overlaps, creation time displays {time} placeholder

Priority: High
Severity: Medium
Affected Area: Web UI – Cloud Platform (Integrations, Run Logs)
Test Environment: Linux Firefox latest version, Mosoo Cloud Platform production environment

---

Description

While using the Mosoo Cloud Platform, three distinct UI/UX issues were observed that impact user operations and data readability:

1. When adding an MCP server, after expanding "Advanced Settings", the content cannot be scrolled vertically, making it impossible to access options (such as the Cancel button) that are out of the visible viewport.

2. When clicking a run log to view details, the event texts in the popup heavily overlap, resulting in a cluttered and unreadable interface.

3. The creation time of the run log displays the literal {time} instead of the actual date/time, leaving users unable to determine when the record was created.

These issues were reproduced on the current production environment as of 2026-08-05.

---

Steps to Reproduce

Issue 1 – Advanced Settings Cannot Scroll

1. Navigate to Cloud Platform > Integrations > MCP Servers.

2. Click the "Add" button to open the new server dialog.

3. Expand the "Advanced Settings" section.

4. Try to scroll down to click the action buttons at the bottom of the dialog.

Actual result: The dialog content is fixed; no scrollbar appears, and mouse wheel or touch gestures are ineffective.

Issue 2 – Run Log Details Text Overlap

1. Go to Cloud Platform > Run > Run Logs.

2. Click any run record (e.g., test under untitled-g53z4u).

3. View the popup detail window.

Actual result: Event entries (e.g., SESSIONEVENTS.EVENT...) are stacked vertically, making them almost illegible.

Issue 3 – Creation Time Missing

1. In the run log detail window, check the header or subtitle area showing creation info.
2. It displays 创建于 {time} (Created at {time}).

Actual result: {time} is not replaced with an actual timestamp; the placeholder remains.

---

Expected Behavior

· The "Advanced Settings" panel should support vertical scrolling (ideally with a scrollbar) to ensure all action buttons are visible and operable.

· The run log detail popup should be well‑formatted, with sufficient spacing between event entries, clear fonts, and no overlap.

· The creation time should display a readable date and time, e.g., 2026-08-05 14:30:22 or a relative time (e.g., "2 hours ago").

---

Actual Behavior

· Advanced settings content is clipped, and the lower part is inaccessible.

· Log events overlap and are difficult to read.

· The timestamp shows {time}, lacking the actual value.

---

Screenshot References

·

– Shows the MCP add dialog with advanced settings expanded but no scrollbar.

·

– Shows the run log detail with overlapping events and {time} displayed.

·
– Confirms the header shows "Created at {time}".

---

Additional Information

· The issues occur under the Default App context within Woods Chen's Organization.

· No console errors were observed; they are likely CSS layout or data‑binding problems.

· These issues significantly affect the efficiency and experience of debugging and configuration tasks.

---

Suggested Fixes

· Scrolling issue: Add overflow-y: auto and a fixed max-height to the dialog content container to enable scrolling when content overflows.

· Overlap issue: Review the CSS for the event list; increase line-height appropriately and avoid absolute positioning conflicts to ensure each event appears on its own line.

· Timestamp issue: Verify the frontend‑backend data binding to ensure a valid timestamp is returned from the backend and correctly formatted by the frontend.

---

Test Environment

· Platform: Mosoo Cloud (cloud.mosoo.ai)

· Relevant URLs: https://cloud.mosoo.ai/integrations/mcp and the /run page

· Browser: Firefox,and the page language is set to Chinese.

· OS: Debian 12

---

Reported by: Mr.C.Woods
Date: 2026-08-05
Labels: bug, UI/UX, cloud-panel, usability

[Yevanchen]

All three reported defects are fixed on main. Closing.

1. MCP "Advanced Settings" cannot scroll — fixed by #500 (77b5c486). DialogContent in the add/edit MCP dialogs is now capped at max-h-[calc(100dvh-2rem)] with a grid-rows-[auto_minmax(0,1fr)_auto] layout, and the form body scrolls independently (min-h-0 overflow-y-auto), so the footer buttons (Cancel/Add) stay reachable on short viewports.

2. Run log detail text overlap — fixed by #500. The event-type chips were rendering raw uppercase i18n keys (e.g. SESSIONEVENTS.EVENTSESSIONSTATUS) because the label helper was called without the active translator; those long keys overflowed the fixed-width chip column into the adjacent event text, which is the overlap in your screenshot. The chips now render short translated labels (all 13 event-label keys exist in en/zh-CN/zh-TW/ja), and each event sits cleanly on its own row.

3. "创建于 {time}" placeholder — fixed by #522 (9af6df76). The translation catalogs used single-brace {time} while the runtime t() only interpolates {{time}}, so the placeholder rendered literally. The catalogs now use {{time}} and the header shows the actual relative creation time. #523 adds a regression test that fails CI if a single-brace placeholder ever reappears in any locale catalog.

Verification (local, current main):

• apps/web unit/regression suite: 235 pass, 0 fail — includes the fix(web): finish reported i18n and dialog polish #500 regression tests for the dialog scroll layout and event-label translation, and the catalog placeholder guards.
• Deterministic browser e2e (just e2e deterministic session-log): 2/2 pass — asserts the run log renders no raw sessionEvents.event* keys, and that the MCP dialog body scrolls with the Cancel button on-screen in a 900×500 viewport.
• Manual browser replay (zh-CN) of the three reported screens confirmed: dialog scrolls to the footer, run-log rows render translated chips with no overlap, and the header shows 创建于 <relative time> instead of {time}.

The fixes reach cloud.mosoo.ai with the next production deploy. Thanks for the detailed report and screenshots, Mr.C.Woods — they made the root causes straightforward to pin down.