material-components / material-components/material-components-android

[MaterialContainerTransform] Element transition not being retained when opening a nested screen

Open
#2,197 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug Feature: Transition
Dominant language
Java
Stars
17.4k
Forks
3.2k
PR merge metrics
No merged PRs in 30d

Description

**Description:**
Once we open "SCREEN A" from "HOME SCREEN" with Material Container Transform it works fine and does the return transformation too. But if we open another activity "SCREEN B" from "SCREEN A" then "SCREEN A" loses its transformation settings.

**Expected behavior:**
"SCREEN A" material container should retain how it was launched and return back in the same transition.

**Android API version:** 30

**Material Library version:** 1.3.0

**Device:** Pixel 2XL

**Screenshot/Video:**
Screen 1: List of arts
Screen 2: Art details
Screen 3: Artist details

We open "SCREEN 2" by clicking on art on "SCREEN 1", it follows enter and exit material transformation. But when we open "SCREEN 3" from "SCREEN 2" then "SCREEN 2" loses its material transform property.

https://user-images.githubusercontent.com/7822179/116664387-05b7b680-a9b6-11eb-9782-e243022b4d39.mp4

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the three-screen flow described in the issue on Android API 30 with Material Library 1.3.0, using the linked video as a reference. Trace how the Material Container Transform is configured when opening Screen 2 and then Screen 3; done means Screen 2 retains its launch settings and returns with the same transition.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, java
Domain
mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.