Why match_parent ≠ EXACTLY: Unraveling Android MeasureSpec Modes

In this installment of the "Android Easy‑Mistake" series, the author tackles a frequent interview question: whether match_parent always maps to MeasureSpec.EXACTLY and wrap_content to MeasureSpec.AT_MOST. The short answer is no – the resulting mode also depends on the parent container’s measurement mode.

How MeasureSpec Is Calculated

When a View is measured, its MeasureSpec is derived from two sources:

The LayoutParams value set on the view (match_parent, wrap_content, or an explicit size).

The spec mode of the parent container (EXACTLY, AT_MOST, or UNSPECIFIED).

The Android framework uses the static method ViewGroup.getChildMeasureSpec to combine these inputs. A simplified version of the method is shown below:

public static int getChildMeasureSpec(int spec, int padding, int childDimension) {
    int specMode = MeasureSpec.getMode(spec);
    // ... compute resultMode based on specMode and childDimension ...
    return MeasureSpec.makeMeasureSpec(resultSize, resultMode);
}

Inside the method, a switch on specMode determines the child’s mode:

If specMode == EXACTLY, a child with a concrete size or match_parent receives EXACTLY; wrap_content receives AT_MOST.

If specMode == AT_MOST, both match_parent and wrap_content end up as AT_MOST unless a fixed size is provided.

If specMode == UNSPECIFIED, the child’s mode becomes UNSPECIFIED unless a concrete size forces EXACTLY.

When Does UNSPECIFIED Appear?

Although many developers think MeasureSpec.UNSPECIFIED is rare, it shows up in several real‑world scenarios:

RecyclerView items that are wrap_content inside a scrolling list receive an UNSPECIFIED height/width during measurement.

NestedScrollView and ScrollView (both extending FrameLayout) measure their children twice; the first pass uses UNSPECIFIED for the height.

Custom ViewGroup s that allow children to be larger than themselves can deliberately request UNSPECIFIED mode.

Key Takeaways

The final MeasureSpec mode is not dictated solely by XML attributes; it is the result of the parent’s spec mode combined with the child’s LayoutParams. Understanding this interaction helps avoid layout bugs and prepares you for interview questions that probe deeper Android UI knowledge.