Hashed routing to named elements

[guardrex]

Fixes #29105

Surayya ... I didn't guess about what general rules or gotchas 😈 that you want to call out. Let me know what you'd like to add in a comment, or you can suggestion them into the text.

---

Internal previews

📄 File	🔗 Preview link
aspnetcore/blazor/fundamentals/routing.md	ASP.NET Core Blazor routing and navigation

[surayya-MS]

Looks great!

[guardrex]

brb ... was pulled off on something else. 🏃

[guardrex]

@surayya-MS ... I feel we can flesh it out a bit more. See my last commit for what I think are improvements.

btw ...

Is the no leading forward slash for the self-links by design?

Does <a href="/hashed-routing#targetElement"> (with a / on it) 💥 at runtime? If so, we might want to work that into the coverage. If that doesn't break, I wonder if we should use it in the href cases for consistency with the Index and Counter component examples?

[surayya-MS]

@surayya-MS ... I feel we can flesh it out a bit more. See my last commit for what I think are improvements.

btw ...

Is the no leading forward slash for the self-links by design?

Does <a href="/hashed-routing#targetElement"> (with a / on it) 💥 at runtime? If so, we might want to work that into the coverage. If that doesn't break, I wonder if we should use it in the href cases for consistency with the Index and Counter component examples?

No, both "/hashed-routing#targetElement" and "hashed-routing#targetElement" will work.

[guardrex]

I just realized that I did have the leading forward slash on the NavigateTo examples, at least in this topic. I'm going to note a tracking item to check the whole Blazor docs node and confirm consistent display later.

[guardrex]

Ok ... this looks good. I'll merge it after it builds out. Thx for your help.