Fixed
Status Update
Comments
il...@google.com <il...@google.com>
jb...@google.com <jb...@google.com>
ap...@google.com <ap...@google.com> #2
I created a thread on the android-developers forum related to this bug:
http://groups.google.com/group/android-
developers/browse_thread/thread/6caa57135927e242/86d4d895e88a5ebb?
lnk=gst&q=custom+account#86d4d895e88a5ebb
developers/browse_thread/thread/6caa57135927e242/86d4d895e88a5ebb?
lnk=gst&q=custom+account#86d4d895e88a5ebb
il...@google.com <il...@google.com> #3
My personal theory is that Google broke this part of the API intentionally to keep
the lock-in on sync functionality they've enjoyed since Android 1.0.....
the lock-in on sync functionality they've enjoyed since Android 1.0.....
Description
Component used: Fragment
Version used: 1.3.0-alpha07
It would be nice to have a way to retrieve the topmost fragment (i.e., the last added fragment) from a
FragmentContainerView
, particularly if it used the same technique asfindViewById()
to cast the Fragment to the right type.This would be particularly helpful when using View Binding or Data Binding where you have easy access to the
FragmentContainerView
instance, but not necessarily to itsR.id
to pass intofindFragmentById()
.With this, you could then write code such as: