Location override using "Sensors" pane in the Chrome/Edge dev tools

[guardrex]

Description

Per dotnet/aspnetcore#53707 (comment).

Hisham ... I'll float something to address this and ping you on the PR. The easy thing to do would be to cross-link to the product unit issue remark in the last section, and perhaps I'll do that. However, I might write something on this.

BTW -- I'd also like to touch that existing PU issue cross-link. We should have link text, and we have a link text format for PU cross-links. I'll drop that into the PR as well.

Also ... This problem that the dev faced came up in the context of a Blazor app. Therefore, I'll need to address it in the Blazor glob/loc article, too. I'll get that on the PR.

Page URL

https://learn.microsoft.com/en-us/aspnet/core/fundamentals/troubleshoot-aspnet-core-localization?view=aspnetcore-8.0

Content source URL

https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/fundamentals/troubleshoot-aspnet-core-localization.md

Document ID

9a1dccda-d7bf-1eb5-e5e3-8aba4aeb444f

Article author

@hishamco

[hishamco]

I will look at the linked comment, so I can understand how it's related to the troubleshooting article that I wrote long time ago

[guardrex]

Ok ... Halter floated the idea that it would go here. I guessed the same.

The article could use some NIT touches, mostly per our style manual. Even if we don't add the sensors bit to this article, I'll perform a quick edit.

[guardrex]

BTW ... If you'd rather work on this issue, that's totally cool with me. However, let me get a PR merged first for this article with these updates. I've already started working on it, and it will be up shortly. After that merges, you can take over and work this issue if you want to.