> e.g. these 33 timezone names ... could use and report as Europe/Paris
Compat/usability i am unsure of here, is websites using timezone name to provide the web content language - e.g. in Portugal google search kindly provided Portuguese despite my locale being en-US - the laptop was on portugal time, you see (automatic OS change). I have no idea how widespread this is, or if it's even good practice - I would have expected best practice would be to respect the locale/requested-web-content language(s)
Bug 1719738 Comment 6 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
> e.g. these 33 timezone names ... could use and report as Europe/Paris
Compat/usability i am unsure of here, is websites using timezone name to provide the web content language - e.g. in Portugal google search kindly provided Portuguese despite my locale being en-US - the laptop was on portugal time, you see (automatic OS change). I have no idea how widespread this is, or if it's even good practice - I would have expected best practice would be to respect the locale/requested-web-content language(s)
edit: a mitigation option here (is this is an actual issue) would be to report the timezone based on the language part of navigator.language (so `en` from `en-US`) - this wouldn't add entropy: e.g.
- pl would be Europe/Warsaw, fr would be Europe/Paris, a non-match would need to fallback to something in our group