-
Notifications
You must be signed in to change notification settings - Fork 974
toLocale* methods not respecting locale #5879
Comments
The page is using Date.prototype.toLocaleTimeString() which may be causing the issue This would be a good chance to also use |
After talking this out more, it could be a bigger problem. The formatting here should be picked up properly. Current production builds use the same locale that is picked in about:preferences and functions like Number.prototype.toLocaleString() and Date.prototype.toLocaleTimeString() work as expected We may need to enable internationalization when building node/v8: |
Here's a JSBin you can execute to show that no other locales are working in the 54 build, it returns |
also affects history and likely affects bookmarks manager; see: |
OK this one has been not so fun. I want to take a few minutes and document the problem and what I've tried to solve it. building Muon (our fork of Electron) from sourceBuilding
The build has a structure like this:
Both Node and Muon depend on v8 and must use the same version (if you try to include both, there'll be an issue since singleton classes are involved). The previous Electron (before gn builds) was compiling node without i18n support because it uses the resource files from libchromiumcontent (which no longer exists for us). The solution to all of this is: update our fork of Node to use the same v8 that's included in Chromium.
We need to build v8 with international support. Here are some diffs from what I think should solve the issue: brave/browser-laptop-bootstrap
brave/electron
Current statusOn macOS, this compiles and links but crashes with this error being written to the console: macOS will bring up a dialog to report the error, from which you can get a crash report. Here are the relevant bits:
|
fixed, just narrowing down what was actually needed |
Re-opening for Windows. |
Test plan: available on the 1st post. |
I added |
Did you search for similar issues before submitting this one?
No
Describe the issue you encountered:
When trying the 0.13.0 Preview1 build, I found the new tab page showed a lot more info than before.
Stats are wrapping.
Expected behavior:
New tab page should look the same as before.
Platform (Win7, 8, 10? macOS? Linux distro?):
Tested on OS X
Brave Version:
0.13.0 Preview 1
Steps to reproduce:
Screenshot if needed:
0.13.0 Preview1 / Chromium 54 tracking issue #5877
http://jsbin.com/tihayoy/edit?html,js,output
The text was updated successfully, but these errors were encountered: