[Bug]: Chosen date in the V9 DatePicker does not respect user's language settings. It always shows in English. about fluentui

[Hotell]

I don't have proper context but I'm curious how We do not need to do anything when we use the old date picker, the chosen date is automatically translated, but after the migration, the chosen date is always in English is actually working, as that needs to be done within application code based on language setting fetched from user browser.

Briefly looked at the v8 and v9 format/value implementation and it is the same so I'm not sure the behaviour that "just works" is actually what is happening.

This demo shows that there is no auto translation in place for v8 control

I'll leave this to the SME on this control @sopranopillow

ty

[layershifter]

We had conversation about this in offline.

For context, v0 DatePicker used strings prop to also localize the input, v9 one requires to use onFormatDate as documented in the examples. Both datepickers don't have built-in localization by design. Closing it.

[Hotell]

v0 DatePicker

@layershifter this is about v8 version previous behaviour .