From fa1965e31669fcaeffa19d40c1b76fd9623d78da Mon Sep 17 00:00:00 2001 From: Aurimas Liutikas Date: Wed, 8 Jun 2016 17:38:38 -0700 Subject: [PATCH] Swap fill_parent with match_parent in best practices doc. Bug: https://code.google.com/p/android/issues/detail?id=61600 Change-Id: I86ef4f69800c3271fe6e4a5b09a184b2de7f6bc9 (cherry picked from commit 309e97fc3c05135261d6c5e4ac054e53f081637c) --- docs/html/guide/practices/screens_support.jd | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/html/guide/practices/screens_support.jd b/docs/html/guide/practices/screens_support.jd index 9faa6a6f05d4d..1f5f472704e23 100644 --- a/docs/html/guide/practices/screens_support.jd +++ b/docs/html/guide/practices/screens_support.jd @@ -988,7 +988,7 @@ configurations.

on different screens:

    -
  1. Use {@code wrap_content}, {@code fill_parent}, or {@code dp} units when specifying +
  2. Use {@code wrap_content}, {@code match_parent}, or {@code dp} units when specifying dimensions in an XML layout file
  3. Do not use hard coded pixel values in your application code
  4. Do not use {@code AbsoluteLayout} (it's deprecated)
  5. @@ -998,7 +998,7 @@ dimensions in an XML layout file

    The following sections provide more details.

    -

    1. Use wrap_content, fill_parent, or the dp unit for layout dimensions

    +

    1. Use wrap_content, match_parent, or the dp unit for layout dimensions

    When defining the {@code android:layout_height} for views in an XML layout file, using "wrap_content", -"fill_parent" or dp units guarantees that the view is +"match_parent" or dp units guarantees that the view is given an appropriate size on the current device screen.

    For instance, a view with a layout_width="100dp" measures 100 pixels wide on