FragmentContainerView should not serve views that do not contain a Fragment [136494650]

Fixed

Feature Request

Status Update

No update yet.

Description

jb...@google.com

created issue #1

Jul 1, 2019 08:47PM

In most cases, there is no need for a view to consider the contents of its children, but because the behavior of FragmentContainerView is specifically for Fragments, this is a special case.

When views that do not container Fragments attempt to be added to a FragmentContainerView an error should be thrown.

A findFragment() API should be added to FragmentContainerView to allow it to identify the Fragment within a view.

Comments

ap...@google.com <ap...@google.com> #2Jul 26, 2019 10:04PM

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.

ap...@google.com <ap...@google.com> #3Jul 29, 2019 05:39PM

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

jb...@google.com <jb...@google.com> #4Jul 29, 2019 05:40PM

Marked as fixed.

This has been fixed internally and will be available in the Fragment 1.2.0-alpha02 release.

Issue 136494650

Description

Issue summary

Comments

ap...@google.com <ap...@google.com> #2Jul 26, 2019 10:04PM

ap...@google.com <ap...@google.com> #3Jul 29, 2019 05:39PM

jb...@google.com <jb...@google.com> #4Jul 29, 2019 05:40PM

Add comment

Issue metadata