fix: restore HeadOutlet for proper Blazor framework initialization
TaxBaik CI/CD / build-and-deploy (push) Successful in 2m15s
TaxBaik CI/CD / build-and-deploy (push) Successful in 2m15s
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 <noreply@anthropic.com>
This commit is contained in:
@@ -19,6 +19,7 @@
|
|||||||
window.location.pathname.toLowerCase().endsWith('/admin/login'));
|
window.location.pathname.toLowerCase().endsWith('/admin/login'));
|
||||||
</script>
|
</script>
|
||||||
<link rel="stylesheet" href="css/admin.css" />
|
<link rel="stylesheet" href="css/admin.css" />
|
||||||
|
<component type="typeof(HeadOutlet)" render-mode="InteractiveWebAssembly" />
|
||||||
</head>
|
</head>
|
||||||
<body>
|
<body>
|
||||||
<div id="components-reconnect-modal" class="admin-reconnect-modal">
|
<div id="components-reconnect-modal" class="admin-reconnect-modal">
|
||||||
|
|||||||
Reference in New Issue
Block a user