Merge lp:~zaspire/oxide/navigator-language into lp:~oxide-developers/oxide/oxide.trunk
Proposed by
Maxim Ermilov
Status: | Merged | ||||
---|---|---|---|---|---|
Merged at revision: | 1016 | ||||
Proposed branch: | lp:~zaspire/oxide/navigator-language | ||||
Merge into: | lp:~oxide-developers/oxide/oxide.trunk | ||||
Diff against target: |
66 lines (+14/-0) 5 files modified
qt/core/browser/oxide_qt_browser_platform_integration.cc (+5/-0) qt/core/browser/oxide_qt_browser_platform_integration.h (+1/-0) shared/browser/oxide_browser_platform_integration.h (+2/-0) shared/browser/oxide_content_browser_client.cc (+5/-0) shared/browser/oxide_content_browser_client.h (+1/-0) |
||||
To merge this branch: | bzr merge lp:~zaspire/oxide/navigator-language | ||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Chris Coulson | Approve | ||
Review via email: mp+253314@code.launchpad.net |
To post a comment you must log in.
Thanks, this looks fine.
I believe there might also be a second bug - in oxide:: ContentMainDele gate::PreSandbo xStartup we call ui::ResourceBun dle::InitShared InstanceWithLoc ale with an empty locale to rely on Chromium to select the correct locale (and load the right resource file, which is needed to get the correct Accept-Language header). But this only works when Chromium is built with the glib bits turned on, which I don't think we do anymore. If that's the case, we also need to pass the application locale to InitSharedInsta nceWithLocale (it would mean adding a second method - PlatformDelegat e::GetApplicati onLocale - in addition to the one added in this merge).
Would you mind taking a look at that too?