kjh2064
79d99cfd7a
TaxBaik CI/CD / build-and-deploy (push) Successful in 1m23s
**Issue**: Loading indicator (spinner) continues to display even after page fully loads **Root cause**: - Blazor.start() was already called by blazor.web.js (auto-starts) - Calling it again in JavaScript won't trigger promise resolution - Promise callback never executed, overlay never hidden **Solution**: Use multiple detection methods to ensure loading hides: 1. Blazor 'ready' event listener (when circuit is ready) 2. DOMContentLoaded + 500ms timeout (fallback) 3. MutationObserver watching for 20+ MudBlazor components **Result**: - Loading spinner shows: page load starts - Spinner hides: when ANY of the above conditions met (whichever is first) - No more stuck loading indicator This ensures loading always hides regardless of how Blazor initializes. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>