breautek commented on issue #283: URL: https://github.com/apache/cordova-plugin-statusbar/issues/283#issuecomment-3312732915
> confirmed targeting API 35 and StatusBar works fine. change to API 36 and the app overlays the StatusBar. in API 36 I believe edge-to-edge mode is enforced, which means all apps will have an overlaid status bar whether you like it or not and app developers will be responsible for positioning their content appropriately. The "correct" way is to use the safe area inset CSS vars so you can pad your content that shouldn't be underneath the statusbar, or notch. Because Google is Google however, I believe that is unreliable, because historically these CSS vars never worked in the android webview. I heard they were fixed in a recent webview release but I haven't had a chance to test it, and you can't necessary guarantee that your users are running the latest webview version either. In my apps, I've always had an overlaid status bar and edge-2-edge look to begin with, so I didn't experience any "breaking" change. We also work around the unreliable safe area inset CSS vars using a plugin that we wrote (https://github.com/totalpaveinc/cordova-plugin-insets), which allows you to fetch and listen for safe area inset as reported from the native framework instead of using the browser feature. The plugin is fairly un-opinionated, you get them in JS, up to you how you want to consume the inset info. A common way is to create custom CSS vars from that data so you can use the information in your CSS. I'm not sure how Apache is planning on addressing this the plugin approach could be a valid approach to workaround browser safe area inset issues. -- 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]
