commit | 4be84bb10cf0bd998f33d9e5a7ca42cf8e072ad7 | [log] [tgz] |
---|---|---|
author | Adam Powell <adamp@google.com> | Wed Apr 27 13:45:38 2016 -0700 |
committer | Adam Powell <adamp@google.com> | Wed Apr 27 13:45:38 2016 -0700 |
tree | f87d9e3ffe8ed178b7f620af9d9f807f2dd0ba87 | |
parent | 9f72683feed14cba29d8c7189269a48e01f98489 [diff] [blame] |
Don't lose content change during rollback for loader already started Framework edition If a loader is already started when we try to rollback a content change, force a new load instead of simply setting the flag to refresh next time. Bug 28406183 https://code.google.com/p/android/issues/detail?id=208278 Change-Id: If11d79088d30dd2dc48cf1b3d2882f3712b6cddb
diff --git a/core/java/android/content/Loader.java b/core/java/android/content/Loader.java index e9d82af..c5e0ea7 100644 --- a/core/java/android/content/Loader.java +++ b/core/java/android/content/Loader.java
@@ -484,7 +484,7 @@ */ public void rollbackContentChanged() { if (mProcessingChange) { - mContentChanged = true; + onContentChanged(); } }