don't run the loading animation during setup/teardown
s/Runnable/FragmentRunnable/g
That ensures any delayed work, especially animation, is ignored
after Fragment removal. It's okay to drop it because subsequent
creation will take it through all necessary states again.
When restoring the activity, fragments go through transient
visibility changes that may also try to run the dismiss
animation. Disable the animation and immediately jump to the
final state when fragment is not yet added.
Fix catching exceptions in deferred JS bridge methods.
Bug: 7403314
Change-Id: I43170efe598dfc686adb41a589c4814d68a4aa30
2 files changed