From a2385ac3994881b58fa06c96387868821ce5c7d8 Mon Sep 17 00:00:00 2001 From: Chris Li Date: Wed, 27 Jul 2022 22:28:27 +0800 Subject: [PATCH] Update ActivityEmbedding Property Javadoc Bug: 240387168 Test: Javadoc change only Change-Id: I65d2cbbd5039a3bcc023ad1c344ecff1e0991998 --- core/java/android/view/WindowManager.java | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/core/java/android/view/WindowManager.java b/core/java/android/view/WindowManager.java index 70a690c3f264a..e56c43e57aa0e 100644 --- a/core/java/android/view/WindowManager.java +++ b/core/java/android/view/WindowManager.java @@ -824,16 +824,20 @@ public interface WindowManager extends ViewManager { * provide consent for their app to allow OEMs to manually provide ActivityEmbedding split * rule configuration on behalf of the app. * - *

If {@code true}, the system CAN override the windowing behaviors for the app, such as + *

If {@code true}, the system can override the windowing behaviors for the app, such as * showing some activities side-by-side. In this case, it will report that ActivityEmbedding * APIs are disabled for the app to avoid conflict. * - *

If {@code false}, the system MUST NOT override the window behavior for the app. It should + *

If {@code false}, the system can't override the window behavior for the app. It should * be used if the app wants to provide their own ActivityEmbedding split rules, or if the app * wants to opt-out of system overrides for any other reason. * *

Default is {@code false}. * + *

The system enforcement will be added in Android 14, but some devices may start following + * the requirement before that. The best practice for apps is to always explicitly set this + * property in AndroidManifest instead of relying on the default value. + * *

Example usage: * 

      * <application>