This happens inside ui::PathProvider() in Chromium. We can probably avoid this by registering an override for the ui::DIR_LOCALES key in the path service from Oxide, rather than patching Chromium. This would prevent the provider in Chromium from being called
This happens inside ui::PathProvider() in Chromium. We can probably avoid this by registering an override for the ui::DIR_LOCALES key in the path service from Oxide, rather than patching Chromium. This would prevent the provider in Chromium from being called