breautek commented on issue #1967: URL: https://github.com/apache/cordova-android/issues/1967#issuecomment-4907834724
> But wouldn't this only be configurable at build time? In my app, the theme (light/dark mode) can be controlled by the user in three different ways: Device, Enabled, Disabled. Correct -- you wouldn't have runtime control. Something I thought after I posted lol. > Out of all these, I do think StatusBar.styleLightContent() and StatusBar.styleDefault() should be implemented in the built-in plugin (On both iOS and Android), as they're often needed depending on the app's theme or design. I think I can probably agree with this. I've been kind out of the development loop with Apache but it's my understanding that they tried to keep a very basic statusbar implementation the core -- while continue to support the cordova-plugin-statusbar for more advanced functionality. So this might be a case where the statusbar plugin would be recommended to be installed (or in your case your fork) to maintain access to `.styleLightContent()` and `.styleDefault()` APIs. But that brings back to originally reported conflict I assume right? Where there is a conflict between the core system statusbar setting the status bar appearance overriding the statusbar plugin? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
