When using postponedEnterTransition twice, the first Runnable is not removed [137797118]

Fixed

Bug

Status Update

No update yet.

Description

jb...@google.com

created issue #1

Jul 18, 2019 12:01AM

If using postponedEnterTransition(long, TimeUnit) with a Fragment and it is called twice, the first Runnable is not moved so startPostponedEnterTransition() gets called twice.

The Fragment should maintain the Runnable so it can be removed later.

Comments

ap...@google.com <ap...@google.com> #2Jul 19, 2019 12:04AM

Hi Ed, Thank you so much for these suggestions. I've been reviewing them and merging them in. Hopefully it should be live. I've included a thank you note too in the article.

an...@google.com <an...@google.com> #3Jul 19, 2019 12:24AM

Great! Thanks a lot, I'll look for the live updates soon!

il...@google.com <il...@google.com> #4Jul 19, 2019 12:33AM

Marked as fixed.

This is fixed and will be part of Fragments 1.1.0-rc03

Issue 137797118

Description

Issue summary

Comments

ap...@google.com <ap...@google.com> #2Jul 19, 2019 12:04AM

an...@google.com <an...@google.com> #3Jul 19, 2019 12:24AM

il...@google.com <il...@google.com> #4Jul 19, 2019 12:33AM

Add comment

Issue metadata