# Known Issues (fix after sprint wrap-up) Running list of bugs spotted during manual verification, deferred until the current sprint's feature work is done. Add to this list as more are found; don't fix inline unless asked. ## Open 1. **Homepage hero-to-categories dead space gap on the storefront home page.** Traces to bootstrap mock config (widget/section padding values in the dev bootstrap fixture), not a code defect in `dynamic-page-layout.component.ts` or the widget components - not fixed this session, needs config-side investigation if it reproduces with real tenant data rather than mock config. 2. **~179 untranslated raw i18n keys across the entire admin backoffice CRUD UI (products/categories/orders/transactions/users/monitoring/analytics).** `translations.ts`/`en.ts`/`ru.ts`/`hy.ts` have no `adminProducts.*`, `adminCategories.*`, `adminOrders.*`, `adminTransactions.*`, `adminUsers.*`, `adminMonitoring.*`, or `adminAnalytics.*` sections at all (confirmed: zero matches for any of these prefixes in any of the 4 i18n files). `TranslateService.t()` falls through to returning the raw dotted key string when a key isn't found (see `translate.service.ts`), so every templated string in these features (buttons, table headers, filters, badges, empty/placeholder text) renders literally as e.g. `adminProducts.create` instead of real copy - same root cause as the already-fixed dashboard Quick Actions bug below, just at the scale of almost the entire admin backoffice built across Sprints 20-27. - Counted by grepping all `'adminXxx.yyy'` translate-pipe usages under `src/app/features/admin/**`: `adminProducts` 72, `adminCategories` 23, `adminOrders` 24, `adminUsers` 21, `adminMonitoring` 13, `adminAnalytics` 12, `adminTransactions` 13 (≈178 distinct keys, ×3 locales ≈ 534 strings to author). - Likely why it was never caught: every affected Sprint (20-27) explicitly noted live-browser click-through was blocked on the guarded admin route and verification was tsc/build/arch:check only - none of those catch missing i18n keys (pipe arguments are plain strings, not type-checked). - Found: 2026-07-15, during Sprint 28 manual audit (reading templates + grepping i18n files, not live browser). - **Deferred to Sprint 29** ("translation validation" is explicit Sprint 29 scope per `docs/SPRINT-PLAN.md`) rather than fixed inline during Sprint 28 polish - authoring ~534 correct strings across 3 languages is a large, separate, mechanical pass of its own and shouldn't be rushed inside a polish sprint. Sprint 28 only adds the handful of new keys it introduces itself (empty-state copy for the skeleton/empty-state consistency fix), it does not touch the ~178 pre-existing gap. 3. **Theme Mode selector has no runtime effect.** `theme-section`'s light/dark/ system dropdown saves correctly and `theme-engine.service.ts` sets a `data-theme-mode` attribute on ``, but no CSS anywhere in the app reads that attribute — picking Dark or System changes nothing visually today. Theme palette colors are unaffected (they're real CSS custom properties, genuinely live). Fixing this means implementing actual dark-mode CSS (a dark palette + `[data-theme-mode]`/`prefers-color-scheme` strategy + a `matchMedia` listener for "system", since that can change without a reload) — a real feature project, not a wiring fix. - Found: 2026-07-17, project-editor bug-hunt audit (`docs/EDITOR.md`). 4. **`dynamic-renderer/` pipeline exists but is never wired up.** `src/app/dynamic-renderer/{page-renderer,section-renderer,section-engine, page-resolver,widget-host}` has services and models but zero components or templates (every directory has only a `.gitkeep`). The storefront homepage renders through a separate, older path that doesn't consume it. Two editor fields feed this dead pipeline with no visible effect: `layout.type` (Theme section, "Site Layout") and the homepage section's own `type` field (`homepage-section.component.ts`'s `updateSection(id, 'type', ...)` has no UI calling it, because of this). Needs a decision: finish wiring it in (if it's WIP for a planned replacement) or delete it as abandoned scaffolding. - Found: 2026-07-17, project-editor bug-hunt audit. 5. **`HeaderConfig.showProfile` toggle has no corresponding UI.** The header editor's "Profile" toggle updates a real config field, but `header.component.html` never references `showProfile` — there's no profile/account menu in the storefront header to show or hide. Needs an auth-system check first (does one exist yet?) before building the menu. - Found: 2026-07-17, project-editor bug-hunt audit. 6. **Payment modal / bank-payment iframe on Cart still custom, not `app-dialog`.** Has its own multi-step state and focus-trap already — migrating to the shared dialog primitive is a composition change, deliberately left out of RC-Premium-01's visual-polish scope. - Found: 2026-07-23, RC-Premium-01 (`docs/STORE_FRONT_UX_REVIEW.md`). 7. **Cart's `clearCart()` uses native `confirm()`, no styled confirm dialog.** No existing storefront pattern for a confirm-remove dialog to follow yet — introducing the first one is an architecture decision, not polish. - Found: 2026-07-23, RC-Premium-01. 8. **`stars.component` rating glyph color and a few legacy hex literals in `pages/category`/`pages/search` have no exact design-token match.** Left as literals to avoid an unintended visual shift; needs a deliberate token-extension decision before normalizing. - Found: 2026-07-23, RC-Premium-01. 9. **`pages/category` and `pages/search` still use hand-rolled skeleton markup instead of `app-skeleton`.** Composition-level fix (RC-Visual-02 territory), not touched during RC-Premium-01's visual-polish pass. - Found: 2026-07-23, RC-Premium-01. 10. **Cart's `.email-form` block (post-payment email/phone capture) is dead CSS behind commented-out markup.** Candidate for deletion in a cleanup pass; not removed during RC-Premium-01 (out of scope for a polish pass). - Found: 2026-07-23, RC-Premium-01. ## Fixed 1. **Full-project UX/UI + motion pass across storefront, admin dashboard, admin CRUD, and project-editor.** User asked (2026-07-16) for a full UX/UI audit across admin, dashboard, and storefront, sequenced: storefront -> admin dashboard -> admin CRUD -> project-editor. All 4 phases completed: - Fixed: `project-editor-save-bar` buttons were plain unstyled `