Bottom Navigation View切换非Home Fragment时收缩问题求助

Looks like you're hitting a common layout instability issue with BottomNavigationView, specifically when navigating away from your Home Fragment. Let's break down the possible causes and fixes based on your provided layout files:

Possible Root Causes #

The shrink behavior is likely triggered by:

• Dynamic layout resizing from your Home Fragment (e.g., scrollable views like RecyclerView/NestedScrollView causing parent layout redraws)
• Weight-based layout nesting in your LinearLayout setup, which can lead to unexpected height calculations during fragment transitions
• Unstable layout parameters for the BottomNavigationView that let it get squeezed when the content area changes

Step-by-Step Fixes #

1. Fix BottomNavigationView Height First (Quick Win) #

Your current BottomNavigationView uses wrap_content for height, which can let it shrink if the parent layout recalculates space. Try locking its height to a fixed value (matching the action bar size is a standard approach):

<!-- In app_bar_main.xml -->
<android.support.design.widget.BottomNavigationView 
    android:id="@+id/navigation" 
    android:layout_width="match_parent" 
    android:layout_height="?attr/actionBarSize" <!-- Fixed height -->
    android:background="?android:attr/windowBackground" 
    app:menu="@menu/navigation" />

This ensures the bottom nav stays at a consistent height regardless of content changes.

2. Check Home Fragment Layout for Scrollable Elements #

If your Home Fragment contains a RecyclerView, NestedScrollView, or other scrollable component, make sure:

• Its android:layout_height is set to match_parent (not wrap_content)
• You haven't added any app:layout_behavior attributes that might trigger unexpected layout shifts
• There's no code in the Home Fragment that modifies the parent FrameLayout's layout parameters dynamically

3. Refactor Layout to ConstraintLayout (More Stable) #

LinearLayout with nested weights can be prone to layout redraw issues. Switching to ConstraintLayout gives you precise control over component positioning and eliminates weight-related instability:

<!-- Updated app_bar_main.xml with ConstraintLayout -->
<?xml version="1.0" encoding="utf-8"?>
<androidx.constraintlayout.widget.ConstraintLayout 
    xmlns:android="http://schemas.android.com/apk/res/android"
    xmlns:app="http://schemas.android.com/apk/res-auto"
    android:layout_width="match_parent"
    android:layout_height="match_parent">

    <android.support.design.widget.AppBarLayout
        android:id="@+id/app_bar"
        android:layout_width="match_parent"
        android:layout_height="wrap_content"
        android:theme="@style/AppTheme.AppBarOverlay"
        app:layout_constraintTop_toTopOf="parent">

        <android.support.v7.widget.Toolbar
            android:id="@+id/toolbar"
            android:layout_width="match_parent"
            android:layout_height="?attr/actionBarSize"
            android:background="?attr/colorPrimary"
            app:popupTheme="@style/AppTheme.PopupOverlay" />
    </android.support.design.widget.AppBarLayout>

    <!-- Content area fixed between AppBar and BottomNav -->
    <FrameLayout
        android:id="@+id/content"
        android:layout_width="match_parent"
        android:layout_height="0dp"
        app:layout_constraintTop_toBottomOf="@id/app_bar"
        app:layout_constraintBottom_toTopOf="@id/navigation" />

    <android.support.design.widget.BottomNavigationView
        android:id="@+id/navigation"
        android:layout_width="match_parent"
        android:layout_height="wrap_content"
        android:background="?android:attr/windowBackground"
        app:menu="@menu/navigation"
        app:layout_constraintBottom_toBottomOf="parent" />
</androidx.constraintlayout.widget.ConstraintLayout>

This setup locks the BottomNavigationView to the bottom of the screen and makes the content area fill the remaining space, eliminating any chance of the nav being squeezed.

4. Verify Fragment Transition Code #

Double-check your fragment replacement code to ensure you're not modifying the content FrameLayout's layout parameters. For example, avoid code like:

// Bad: This can trigger layout redraws
FrameLayout content = findViewById(R.id.content);
content.setLayoutParams(new LinearLayout.LayoutParams(...));

Stick to standard fragment transactions:

getSupportFragmentManager()
    .beginTransaction()
    .replace(R.id.content, new OffersFragment())
    .commit();

Final Notes #

Start with Fix #1 since it's the quickest to test. If that doesn't resolve the issue, move on to checking your Home Fragment's layout, then consider the ConstraintLayout refactor for long-term layout stability.

内容的提问来源于stack exchange，提问作者BLACKMAMBA