breautek commented on issue #1465:
URL: 
https://github.com/apache/cordova-android/issues/1465#issuecomment-1353207897

   I think using `"android:windowLayoutInDisplayCutoutMode"="never"` is not 
really a great fix from a Cordova standpoint. e.g. it's not something we can 
apply generically.
   
   From my understanding based on the [Android 
Docs](https://developer.android.com/develop/ui/views/layout/display-cutout#choose_how_your_app_handles_cutout_areas),
 `never` makes it so the app never consumes the cutout/unsafe space. Which is 
why it kind of fixes the issue but it also strips control away and I assume it 
produces blank space in the unsafe areas, likely black. This is why I think we 
cannot apply this generically The blank space color might be configurable via 
the `BackgroundColor` preference.
   
   We could add a preference to configure this, but if a workaround can be done 
simply by providing a resource-file, I think I'd prefer documenting that 
approach rather than adding a feature option that we would have to maintain 
thereafter, especially since this feature is just for a workaround to an 
upstream chromium bug.
   
   @cxcxcxcx If you could provide a full example of the workaround including 
the contents of `resources/android/xml/themes_v27.xml`, I think that would be 
helpful. I find how to apply the workaround from 
https://github.com/apache/cordova-android/issues/1465#issuecomment-1216730224 
is not completely clear.  Later I can take it and document it to the [Android 
Quirks](https://cordova.apache.org/docs/en/11.x/guide/platforms/android/index.html#android-quirks)
 


-- 
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]

Reply via email to