After updating from com.android.support:support-v13:21.0.0 to com.android.support:support-v13:22.0.0
I noticed a very important change in behaviour of the getView() method of android.support.v4.app.Fragment With version 21, getView() returns a NoSaveStateFrameLayout which then contains as a single child the Layout that was inflated in the Fragments onCreateView method. With version 22, getView() returns the inflated layout itself, without the enclosing NoSaveStateFrameLayout. This is, for me, reproducable on the most simple app (Android Studio wizard, Activity with Fragment) and reproducable all the time. This can cause trouble if you use the getView() method to retrieve the fragment's view at runtime and rely, for example, on the first child of getView() being a ViewGroup of a certain type (LinearLayout, ...). Perhaps someone can explain a. what the NoSaveStateFrameLayout is, b. why it isn't used anymore and c. if the behaviour of com.android.support:support-v13:22.0.0 is intended that way. Best regards, Florian -- You received this message because you are subscribed to the Google Groups "adt-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to adt-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
