fix(web): render resilient inbox rows - #189
Merged
Merged
Conversation
6 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related issue
Closes #188
Plan reference
Phase 3 — Gmail and web: inbox and reading usability; follow-up from the complete UI quality audit.
Summary
Keeps inbox rows complete, legible, and actionable when provider metadata is missing, and localizes row actions consistently with the selected language.
Changes
Validation
Relevant automated checks pass
Manual verification completed where needed
bun run --cwd apps/web test: 50 tests passed.bun run --cwd apps/web typecheck: passed.bun run --cwd apps/web build: passed; existing bundle-size and Tauri dynamic-import warnings remain.go test ./internal/modules/translations: passed.bun run --cwd apps/web test:e2e -- tests/inbox.spec.ts: 6 viewport projects passed after correcting a detected accessible-name regression.Codex integrated browser audit on authenticated production: desktop and mobile geometry had no horizontal overflow; labels, More, context, account, language, and conversation states were exercised before implementation.
Risks and rollback
The change is limited to web row presentation and translation keys. Revert the single commit to restore the prior rendering; no message or provider data is changed.
Checklist
Closesreference identify the same primary issue