From e47dcf34d58acb43527c7dc6c7bdb5ff66f2bc90 Mon Sep 17 00:00:00 2001
From: George Mount <mount@google.com>
Date: Fri, 4 Dec 2020 23:40:04 +0000
Subject: [PATCH] Fix documentation for splitMotionEvents attribute.

Fixes: 174832354

Test: None
Change-Id: I1273866309355bedcebd8284adadd2738f8f2ef9
---
 core/res/res/values/attrs.xml | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/core/res/res/values/attrs.xml b/core/res/res/values/attrs.xml
index 03e64a4038ad1..f4c30634ae046 100644
--- a/core/res/res/values/attrs.xml
+++ b/core/res/res/values/attrs.xml
@@ -3334,11 +3334,11 @@
 
         <!-- Sets whether this ViewGroup should split MotionEvents
              to separate child views during touch event dispatch.
-             If false (default), touch events will be dispatched to
+             If false (default prior to HONEYCOMB), touch events will be dispatched to
              the child view where the first pointer went down until
              the last pointer goes up.
-             If true, touch events may be dispatched to multiple children.
-             MotionEvents for each pointer will be dispatched to the child
+             If true (default for HONEYCOMB and later), touch events may be dispatched to
+             multiple children. MotionEvents for each pointer will be dispatched to the child
              view where the initial ACTION_DOWN event happened.
              See {@link android.view.ViewGroup#setMotionEventSplittingEnabled(boolean)}
              for more information. -->