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

Seems to be a DNS problem with systems that have 'obtain DNS server address automatically'. Changed my system to a manual setting and the browser etc now work. SDK 2.2 didn't seem to mind the auto setting though.

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

Could you please describe how/where you changed your system to a manual setting?

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

Marked as fixed.

Based on its date, this issue was originally reported before Android 2.3. Because of the many changes that existed in Android 4.x compared to previous versions, it's very likely that this issue doesn't exist in recent versions of Android like 4.2.2 or newer. Because of the high likelihood that this issue is obsolete, it is getting closed automatically by a script, without a human looking at it in detail. If the issue still exists on a Nexus 4 or Nexus 7 running Android 4.2.2 and is not related to Google applications, please open a new report accordingly.

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