From 7cfe9f83ac2993578e984cf8f0781b6e365d0732 Mon Sep 17 00:00:00 2001
From: Andrew Solovay <asolovay@google.com>
Date: Tue, 30 Aug 2016 11:34:05 -0700
Subject: [PATCH] docs: Added note about CustomTabsIntent.setAlwaysUseBrowserUI

See first comment for doc stage location.

bug: 31181353
Change-Id: Ibdd8c32be4b182241a4b2d3b4f430dbca18c53fb
---
 docs/html/topic/libraries/support-library/revisions.jd | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/docs/html/topic/libraries/support-library/revisions.jd b/docs/html/topic/libraries/support-library/revisions.jd
index 4e14c7054bbdb..1fe4daa22c2d4 100644
--- a/docs/html/topic/libraries/support-library/revisions.jd
+++ b/docs/html/topic/libraries/support-library/revisions.jd
@@ -174,6 +174,14 @@ APK size, we recommend that you just list the specific modules your app needs.
     behavior similar to {@link android.support.v4.view.ViewPager}.
   </li>
 
+  <li>The Custom Tabs library now allows clients to request the standard
+  browser UI, rather than custom tabs UI, by calling <a href=
+  "/reference/android/support/customtabs/CustomTabsIntent.html#setAlwaysUseBrowserUI(android.content.Intent)">
+    <code>CustomTabsIntent.setAlwaysUseBrowserUI()</code></a>. This behavior is
+    useful in cases where the browser defaults to custom tabs UI but the user
+    has expressed a preference for the standard browser UI.
+  </li>
+
 </ul>
 
 <h3 id="24-2-0-behavior">Behavior changes</h3>