summaryrefslogtreecommitdiff
path: root/core/java
diff options
context:
space:
mode:
authorAdam Powell <adamp@google.com>2016-06-22 23:40:25 +0000
committerAndroid (Google) Code Review <android-gerrit@google.com>2016-06-22 23:40:28 +0000
commit103bd9bf003dcee3d6aa92a4c48d28ebadbc0b97 (patch)
tree18a6d748a30168e369ab84303687cf5fa574031a /core/java
parent9900055575ab5486a0320e5a4687baf51ae45747 (diff)
parent7f46c1b73f421e461a8aed1d7629b00b1b178dbf (diff)
Merge "Clarify Fragment#setUserVisibleHint guarantees in docs"
Diffstat (limited to 'core/java')
-rw-r--r--core/java/android/app/Fragment.java3
1 files changed, 3 insertions, 0 deletions
diff --git a/core/java/android/app/Fragment.java b/core/java/android/app/Fragment.java
index c70d45d0ad2d..6485fe3c7fa8 100644
--- a/core/java/android/app/Fragment.java
+++ b/core/java/android/app/Fragment.java
@@ -1029,6 +1029,9 @@ public class Fragment implements ComponentCallbacks2, OnCreateContextMenuListene
* This may be used by the system to prioritize operations such as fragment lifecycle updates
* or loader ordering behavior.</p>
*
+ * <p><strong>Note:</strong> This method may be called outside of the fragment lifecycle
+ * and thus has no ordering guarantees with regard to fragment lifecycle method calls.</p>
+ *
* <p><strong>Note:</strong> Prior to Android N there was a platform bug that could cause
* <code>setUserVisibleHint</code> to bring a fragment up to the started state before its
* <code>FragmentTransaction</code> had been committed. As some apps relied on this behavior,