Uploaded June 2025 | Updated September 2026, 2 weeks ago

---

In Episode 80 of The Blazor Puzzle, Carl Franklin and Jeff Fritz uncover a sneaky and frustrating bug that crashes a Blazor WebAssembly app with zero helpful error messages. The cause? A name collision in JavaScript—and it’s way too easy to make this mistake without realizing it.

🧩 A simple JS interop call fails silently because of an innocent-looking function name: name.

🛑 The browser doesn’t like it because window.name is already a reserved property, and overwriting it leads to bizarre errors in deep SignalR internals—errors that won’t help you at all.

🔍 What You'll Learn:
✔️ Why window.name is a bad choice for your JS function
✔️ How to avoid global namespace collisions in JavaScript
✔️ Two clean solutions:

Rename the function to something unique (e.g., getNameBlazorPuzzle)

💡 Better yet: use scoped JavaScript interop via a Razor Class Library
✔️ Why scoping your JS inside components is a best practice in Blazor

📦 This is a great reminder for anyone doing JS interop in Blazor—don’t trust global scope!

📫 Got a tricky Blazor bug or interop horror story? Send it to blazorpuzzle@appvnext.com and you might win a Blazor Puzzle mug!

🔗 Resources & Code:
github.com/BlazorPuzzle/Puzzle-80

📌 Want to level up your Blazor testing skills? Subscribe & join the puzzle! 🧩

Get Started Today – Free 30 Day Trial
dxpr.es/NUGET
dxpr.es/FREE-TRIAL

Pricing and Online Demos
dxpr.es/BUY
dxpr.es/DEMOS

We Are Here to Help
dxpr.es/SUPPORT

Follow DevExpress on Social Media
dxpr.es/FACEBOOK
dxpr.es/TWITTER
dxpr.es/BLOGS

Review Customer Testimonials
dxpr.es/TESTIMONIALS
dxpr.es/MARKETPLACE

#DevExpress #Blazor #JavaScriptInterop #WebAssembly #DotNet #BlazorPuzzle #ScopedJS #FrontendDebugging #MicrosoftBuild #WASMGotchas