Came across this issue and posted a repro case to this android issue: http://code.google.com/p/android/issues/detail?id=31116#c4
Basically the fragment manager can restore fragments in a different order as how fragments were added before saving state. This has implications with the z order of fragments, where the fragment that is supposed to be on top is restored to be behind other fragments. Anyone came across this issue before, or is there something I'm missing? Thanks, David. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en --- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
