Frontend issues found during docs work
This page tracks product/UI issues found while preparing public documentation and screenshots. It is not public user guidance and should not be copied into user-facing pages.
Record an issue here when the portal shows something that should be fixed in the product rather than documented around:
- wrong-language text or untranslated labels;
- mixed RTL/LTR behavior;
- clipped, overflowing, or unreadable layout;
- technical/internal text visible to users;
- private or sensitive data exposure risk;
- confusing state, empty state, warning, or error message;
- screenshot blocker caused by UI or unsafe demo data.
For each issue, include the route or screen, locale, observed behavior, expected user-facing behavior, evidence path if available, priority, and frontend commit or range checked.
Open issues
| ID | Priority | Source | Route / screen | Locale | Observed issue | Expected behavior | Evidence | Status |
|---|---|---|---|---|---|---|---|---|
front-2026-05-24-ar-create-task-smoke | P1 | ef4ff268 smoke capture | /tasks?create=1, create-task drawer | ar | Arabic smoke frame confirmed lang="ar" and dir="rtl", but the frame contained Russian task/person/client/project data, residual Russian UI labels such as Клиент / Проект клиента, and a native date placeholder mm/dd/yyyy. | Clean Arabic or neutral demo data, localized visible labels, filled date fields, and no stale LTR/RU first-render state before any public screenshot candidate is accepted. | ar-release-diagnostics.json | Open |
front-2026-05-25-ar-auth-bootstrap | P1 | 9457cf3e docs capture probe with current dirty frontend runtime as draft context | /tasks?create=1, unauthenticated auth screen before create-task drawer | ar | A fresh capture profile with browser locale ar reaches the portal but sees the Russian LTR login screen (lang="ru", dir="ltr"). Self-signup is disabled, and PATCH /api/i18n/context returns 401 before authentication, so the capture flow cannot bootstrap a clean Arabic create-task drawer from a fresh profile. | Either provide a prepared authenticated Arabic demo capture profile/storage state, or let the unauthenticated portal honor an approved locale hint/browser locale and keep lang="ar"/dir="rtl" before login. | tmp/ar-screenshot-candidates/diagnostics/ar-create-task-auth-probe-1779733275364.png | Open |
front-2026-05-25-operation-guards-i18n | P1 | 9457cf3e read-only frontend audit; dirty frontend worktree treated as draft context | /tasks/automation?tab=guards, /automation/operation-guards | en/de/zh/es/fr/kk/ky/ar | Operation guard screens include hard-coded Russian labels and button text, so localized task automation screenshots would leak Russian UI text outside the Russian locale. | Operation guard list, editor, empty states, buttons, field labels, operation types, condition labels, and error/blocked messages should use the portal i18n layer for every supported locale before non-RU screenshots are promoted. | /Users/zalivar/codex/b24-tasks-global/b24-tasks-frontend/frontend/src/modules/portal/pages/OperationGuardsPage.tsx | Open |
Resolved issues
No resolved frontend issues recorded yet.