From 9955079407ee0f46a601b4c295de475a8c1b2008 Mon Sep 17 00:00:00 2001 From: John Reck Date: Sun, 23 Jan 2011 16:00:04 -0800 Subject: Fix onLoaderFinished history group selection logic Bug: 3381283 The issue was caused by the data being updated, causing the onLoaderFinished to re-fire, causing it to re-select the default group. Change-Id: Id651dd73e66d441e730ae35675336761b6e773ce --- src/com/android/browser/BrowserHistoryPage.java | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-) (limited to 'src') diff --git a/src/com/android/browser/BrowserHistoryPage.java b/src/com/android/browser/BrowserHistoryPage.java index 66abd9a..777cfd4 100644 --- a/src/com/android/browser/BrowserHistoryPage.java +++ b/src/com/android/browser/BrowserHistoryPage.java @@ -187,7 +187,7 @@ public class BrowserHistoryPage extends Fragment switch (loader.getId()) { case LOADER_HISTORY: { mAdapter.changeCursor(data); - if (mAdapter.getGroupCount() > 0) { + if (mGroupList.getCheckedItemPosition() == ListView.INVALID_POSITION) { selectGroup(0); } @@ -196,13 +196,7 @@ public class BrowserHistoryPage extends Fragment } case LOADER_MOST_VISITED: { - int preCount = mAdapter.getGroupCount(); mAdapter.changeMostVisitedCursor(data); - if (mAdapter.mHistoryCursor != null - && preCount == 0 - && mAdapter.getGroupCount() > 0) { - selectGroup(0); - } checkIfEmpty(); break; -- cgit v1.1