commit 04f7579a1350af17f700a392f986efd126ccc68b
author Aurimas Liutikas <aurimas@google.com> Tue Jun 07 16:58:51 2016 -0700
committer Aurimas Liutikas <aurimas@google.com> Tue Jun 14 16:51:42 2016 -0700
tree 14c6bb1d6561282b4c9f47571ab26e2fe3c55731
parent 568622de422b98d2b53e0ff33bb79962512adc14

Clarify Fragment construtor javadoc.

Bug:
https://code.google.com/p/android/issues/detail?id=170497
https://code.google.com/p/android/issues/detail?id=55991

Change-Id: I61e1e0fd14afe4c3ab083b858bc1a84e6d0e28bd

fragment/java/android/support/v4/app/Fragment.java

diff --git a/fragment/java/android/support/v4/app/Fragment.java b/fragment/java/android/support/v4/app/Fragment.java
index 36afd9b..b27eb59 100644
--- a/fragment/java/android/support/v4/app/Fragment.java
+++ b/fragment/java/android/support/v4/app/Fragment.java
@@ -390,13 +390,11 @@
      * arguments can be supplied by the caller with {@link #setArguments}
      * and later retrieved by the Fragment with {@link #getArguments}.
      * 
-     * <p>Applications should generally not implement a constructor.  The
-     * first place application code an run where the fragment is ready to
-     * be used is in {@link #onAttach(Activity)}, the point where the fragment
-     * is actually associated with its activity.  Some applications may also
-     * want to implement {@link #onInflate} to retrieve attributes from a
-     * layout resource, though should take care here because this happens for
-     * the fragment is attached to its activity.
+     * <p>Applications should generally not implement a constructor. Prefer
+     * {@link #onAttach(Context)} instead. It is the first place application code can run where
+     * the fragment is ready to be used - the point where the fragment is actually associated with
+     * its context. Some applications may also want to implement {@link #onInflate} to retrieve
+     * attributes from a layout resource, although note this happens when the fragment is attached.
      */
     public Fragment() {
     }