I'd argue this is the wrong design goal: correctness is more important.

I'm in the UK but my work PC's Internet exit node is in New York due to enforced use of corporate proxies, so the time shown to me is 5 hours out. Javascript would report the correct timezone.

It is not possible to correctly identify physical location from IP addresses. Not just because of proxies and VPNs and the accuracy of the data: you can go near a border and find your mobile phone connects to a cell tower in a neighbouring country, without even visiting! IP Geolocation is accurate enough for statistics and marketing but probably shouldn't be used for anything user-facing.

"Tonight: Orange Reddit over-engineers a meme website that any normal person would just make with seven PNG files and getDay()."

It's not pedantic and actually a good question, IMO. One that, IMNSHO, isn't discussed enough.

WASM esp in the browser offers a great opportunity to "Do Things Right" that JS in the browser got all wrong in hindsight. I'm not talking about language design, but about what JS can do, access, control, etc: from telemetry to security issues.

The modern DOM apis show how this can be fixed. But there's no way we can fix "the old APIs" which are also used for fingerprinting, tracking, DOSing clients, breaking your back button, annoying scrolling etc. We can see this clearly in how browsers bolt stuff on, like popup blockers early on, and "copy to clipboard only after a human interaction" or "detect too many dialogs" or "detect CPU hogging".

WASM seems to head in the right direction: sandboxing, careful exposure to resources, proper permission systems etc.

But, as a bystander, I don't see much public discussion on how the WASM runtime/sandbox/layers in browsers can and should be shaped to i) fix and avoid mistakes JS made, and ii) while also having better DX and UX in this regard. As mentioned, just a bystander, maybe this discussion is happening, and I just missed it?