Samir Boulahtit
c9fe717184
Some checks failed
Three more hardcoded English strings in customers/storefront/login.html were still bypassing i18n because they were emitted from Alpine showAlert() calls in <script>: - "Account created successfully! Please sign in." (post-register toast) - "Login successful! Redirecting..." (post-login toast) - "Invalid email or password" (login-error fallback) Same pattern as the earlier forgot/reset-password sweep: defined window.__customerLoginI18n with `tojson` server-rendered values, read them once at function entry as `const i18n = ...`, and swapped each hardcoded string for an i18n property. Two new auth.* keys × 4 locales (registration_success_signin, login_success_redirecting). The third reuses the existing auth.invalid_credentials. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>