title: Wrong locale time in Android webview
body: <p>We have an android app which more or less constists of only a webview, displaying a webapp. At some point, we want to display some timestamp to the user and use the following code</p>
  
  <pre><code>let dateString = new Date().toLocaleTimeString();
  </code></pre>
  
  <p>The problem is, this always produces a 12h time representation (ie with AM/PM, for instance <code>3:15 PM</code> instead of <code>15:15</code>),  even if we set the device to use 24h clock (and the device does respect this setting, because we see the correct time in the statusbar). We also set the device to use German language and removed the english language settings. No luck either. The device locale is used, as our app is shown in the correct language, but the timestrings are still wrong. </p>
  
  <pre><code>window.navigator.language  -&gt; "de-AT"
  new Date().toLocaleTimeString(); -&gt; "6:10:13 PM"
  new Date().toLocaleTimeString(window.navigator.language); -&gt; "18:10:32"
  </code></pre>
  
  <p>At a first glance, the last line seemed as a possible workaround, but if language is for instance "en-US" this will always return 12h format, regardless whether the os is configured for using 24h clock or not.</p>
  
  <p>I'm aware of <a href="https://stackoverflow.com/questions/40398528/android-webview-language-changes-abruptly-on-android-n">this</a> question, which seems somehow related to this issue, but the answers don't work for us. </p>
  
  <p>Using various virtual devices I found out, it still works correctly on chrome 58 (on API 26) but does not work any more on chrome 61 (on API 27). Currently testing at chrome 70 beta, the problem still persists. </p>
  
  <p>It's also important to note, that it works correctly in chrome itself (ie if I display a time stamp in a test website, it uses the system settings), but only fails in the webview.</p>
  
  <p>Our current workaround is to generate timestamps via native app, but that seems rather clumsy. </p>
  
  <p><strong>UPDATE</strong></p>
  
  <p>I know I can do some things on the webapp side like overriding <code>toLocaleTimeString</code> (which in fact, I already did to get the correct format from the native app).</p>
  
  <p>My question is more about: Is there any known changed behaviour (and maybe a setting to reverse this) in the native <code>WebView</code> which causes this issue to happen, because this works/worked like a charm on devices with Chrome &lt;= 58.</p>
  
  <p>In the meantime I filed an issue with chromium, they were able to reproduce it. Maybe this will get fixed in one of the next versions ...</p>
  
  <p><strong>UPDATE 2</strong></p>
  
  <p>The issue is already fixed on google's side and may be rolled out with some future update. In the meantime I will continue to use my current override of <code>toLocaleTimeString()</code> which calls back to the native app ...</p>