@@ -88,8 +88,8 @@ to hold a {@link android.widget.TextView} and a {@link android.widget.Button}:</
8888<pre>
8989<?xml version="1.0" encoding="utf-8"?>
9090<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"
91- android:layout_width="fill_parent"
92- android:layout_height="fill_parent"
91+ android:layout_width="match_parent"
92+ android:layout_height="match_parent"
9393 android:orientation="vertical" >
9494 <TextView android:id="@+id/text"
9595 android:layout_width="wrap_content"
@@ -215,14 +215,14 @@ set the width or height: </p>
215215<ul>
216216 <li><var>wrap_content</var> tells your view to size itself to the dimensions
217217required by its content</li>
218- <li><var>fill_parent </var> (renamed <var>match_parent </var> in API Level 8)
218+ <li><var>match_parent </var> (named <var>fill_parent </var> before API Level 8)
219219tells your view to become as big as its parent view group will allow.</li>
220220</ul>
221221
222222<p>In general, specifying a layout width and height using absolute units such as
223223pixels is not recommended. Instead, using relative measurements such as
224224density-independent pixel units (<var>dp</var>), <var>wrap_content</var>, or
225- <var>fill_parent </var>, is a better approach, because it helps ensure that
225+ <var>match_parent </var>, is a better approach, because it helps ensure that
226226your application will display properly across a variety of device screen sizes.
227227The accepted measurement types are defined in the
228228<a href="{@docRoot}guide/topics/resources/available-resources.html#dimension">
0 commit comments