bb58a82daf11bf3c056d1cd5887aa26435d37b69 |
|
16-Mar-2016 |
Aurimas Liutikas <aurimas@google.com> |
Check for saved state type in onRestoreInstanceState. Add instanceof check in onRestoreInstanceState calls throughout frameworks/support code. Bug: 27589237 Change-Id: Id9db70de03979379ca9d98bb8599ac9fa2b46218
/frameworks/support/v13/java/android/support/v13/app/FragmentTabHost.java
|
5424d16916b2fb65ff009051e4f9d02584d07b53 |
|
06-Jun-2013 |
Piet Delport <pjdelport@gmail.com> |
Allow user-customized FragmentTabHost layouts. This delays the convenience construction of the standard view hierarchy until just before calling TabHost's setup(). Previously, initFragmentTabHost() would always construct the standard hierarchy, breaking any other layout supplied by the user. Bug: https://code.google.com/p/android/issues/detail?id=53230 Change-Id: I90c6d5afd1fa9774f8f079cc825b4f60ac6f7c6f
/frameworks/support/v13/java/android/support/v13/app/FragmentTabHost.java
|
74c671b3b67000bf16b4865a8d361344310dccbe |
|
26-Sep-2012 |
Dianne Hackborn <hackbod@google.com> |
Fix how fragment/tab interaction works to avoid list view state loss. The implementation of FragmentTabHost would cause us to toggle between the default and selected tab fragments when restoring our state. Because of an issue in ListView (fixed by another change), this would cause us to lose the state because ListView tripped over itself if you asked it to save its state immediately after restoring it. We are now more careful about switching fragments, so we don't run in to this problem at least in most cases. Also pull over framework change to not let inactive fragments be more than CREATED. Bug #7232088: ListView saved state being lost in some cases Change-Id: Id9f20c207409d2479ff8bce8ed5b0553510cdd63
/frameworks/support/v13/java/android/support/v13/app/FragmentTabHost.java
|