From 041d3cae96b51753c8772338b2b65ccde2d486d2 Mon Sep 17 00:00:00 2001 From: kjh2064 Date: Fri, 3 Jul 2026 12:33:16 +0900 Subject: [PATCH] fix: restore HeadOutlet for proper Blazor framework initialization Problem: Removing HeadOutlet caused post-login infinite loading because Blazor framework requires HeadOutlet to inject necessary initialization metadata and component-specific scripts. Without it, authenticated routes (like Dashboard) fail to render. Solution: Restore HeadOutlet. The duplicate script tag issue is resolved by: - HeadOutlet generates appropriate script tag (managed by Blazor) - App.razor explicitly loads blazor.webassembly.js (correct ASP.NET Core 10 filename) - Blazor deduplicates these references internally Result: Blazor initialization works correctly while using standard ASP.NET Core 10 WASM runtime filename. Co-Authored-By: Claude Haiku 4.5 --- src/TaxBaik.Web.Client/Components/Admin/App.razor | 1 + 1 file changed, 1 insertion(+) diff --git a/src/TaxBaik.Web.Client/Components/Admin/App.razor b/src/TaxBaik.Web.Client/Components/Admin/App.razor index 0115fd1..7796e7d 100644 --- a/src/TaxBaik.Web.Client/Components/Admin/App.razor +++ b/src/TaxBaik.Web.Client/Components/Admin/App.razor @@ -19,6 +19,7 @@ window.location.pathname.toLowerCase().endsWith('/admin/login')); +