In case it is not clear, this isn't related to the developer tools.  Any plain page will give the wrong (non-preferred according to language settings) result when it executes Date.toLocaleString() when languages are set as in the repro steps.

Have you restarted the browser?

Yes, of course.  I have restarted the browser.  The problem still exists.

Able to reproduce the issue on windows 7 using chrome version 53.0.2785.101 and canary 55.0.2857.0 with the below steps

1. Set Language Preferences in this order: [English (Canada), English (United States), English] And set Chrome to display in English (Canada).
2.run "navigator.language" in console
3.Output :: en-GB

This is observed from old builds M42 (42.0.2311.152 ).For M40 and prior versions not able to set English (Canada) as default language.Please find the attached screen shot for the same.

Marking it as Untriaged to get more inputs from dev team.

Thanks,

Deleted: 642444.png 89.2 KB

	642444.png 89.2 KB View Download

Thank you, kavvaru.

Thanks kavvaru!

It's a well-known result of mapping en-Foo to en-GB for anything other than en-US. 
There are many other cases like that. See bug 99526. 

> set Chrome to display in English (Canada).

On Windows, you can do that?? Hmm... that should not be doable until bug 99526 is fixed. It's not set the UI langauge to en-CA (and other en variants other than en-US and en-GB) on Chrome OS. 

BTW, standalone v8 does not have this issue. (that is, this is a Chrome issue: specifically bug 99526). 

LC_ALL=en_CA.UTF-8 out/rel/d8
V8 version 5.5.0 (candidate)
d8> new Date().toLocaleDateString()
2016-09-14

$ LC_ALL=en_AU.UTF-8 out/rel/d8
V8 version 5.5.0 (candidate)
d8> new Date().toLocaleDateString()
14/09/2016

 Issue 698513  has been merged into this issue.

Any progress update on this?

#11: Yes, you can set the display language to English (Canada). |navigator.language| will show 'en-GB', but the application locale preference (intl.app_locale) is set to "en-CA".

This seems sufficiently different from issue 99526 to keep open as a separate bug worth addressing.

Looks like this bug is blocked by 99526. May be worth chatting with Jungshik about why that bug has remained open for so long. Also, if sufficiently similar, maybe Claudio can tackle 642444 along with this one.

Yes, right. The root cause is bug 99526. Why has it been open so long? Because I haven't managed to get to it. :-) 

Recently, I had a fresh look at it and may have a resolution before long. 

Didn't mean to make that sound pointed :) - just wanted to make sure we were aware of any complexity. Jungshik - you and Claudio should connect over VC sometime soon since you have so much context on this and related issues. For context, Claudio is tackling various issues surrounding language settings.

Don't worry. I didn't take it that way. Smiley was not enough. :-)  Sorry for giving that impression. 

Thank you for connecting me with Claudio. We'll for sure coordinate.  

I had a first look at this and it seems unrelated to the rest of the Language bugs that Yana and I are currently working on.
Most likely I won't fix this before having fixed the rest of Language bugs.

Jungshik, I'll keep an eye on bug 99526.
If you have any insight that you want to share for this bug (642444), feel free to reach out to me.

Jshin - reassigning this back to you since claudio is now on ChromeOS.

Just so you know, Microsoft Edge and Firefox both do the right thing.  All dates appear correctly (as en-CA) in other browsers I've tried.  Only Chrome is forcing it to en-GB.

I hate to see Chrome lose ground like this, but it means that I'm faced with recommending that users who are really complaining should switch browsers to resolve the issue.  I really don't want to recommend anything but Chrome.  So please fix this soon.

As of Chrome 67.0.3396.87 this seems to be fixed.

Now when I enter navigator.language in the console, it correctly reports en-CA.

My sincerest thanks to whoever fixed it!