summaryrefslogtreecommitdiff
path: root/src/com/android/browser/BrowserBookmarksAdapter.java
diff options
context:
space:
mode:
authorRobin Humble <plaguedbypenguins@gmail.com>2014-06-08 07:18:55 +0200
committerLorDClockaN <davor@losinj.com>2014-06-08 07:19:22 +0200
commite4cb677f406fd7bedd5b3ee7ff6e249c2b6eb68f (patch)
tree415683915b8ac310fc77dd25a234b17916c6875e /src/com/android/browser/BrowserBookmarksAdapter.java
parent7fa622f559cfb6a504b281c4cb56077683d96d63 (diff)
reduce cookie tracking (4/4): onResume deletion of cookiesHEADkitkat
Optionally delete unwanted cookies (and localstorage) at every Browser resume. The default for this feature is off - ie. maintain the current Browser "keep every cookie" behaviour. Optionally localstorage files (site databases) are also removed whenever cookies have been deleted. This helps to reduce evercookie/supercookie persistence. A whitelist of sites that are permitted to keep cookies is stored in the standard Browser shared_prefs. The site's cookie preference is set via a menu checkbox when viewing the page. This allows opt-in whitelisting behaviour on a per-site basis, suitable for saving eg. login cookies. The cookie deletion itself is done by using existing API's to delete all cookies and then selectively restore just those from the whitelisted sites. Cookie counting is the only new API needed by this patch, and is used to eliminate unnecessary cookie and localstorage deletes. Although simplistic, onResume cookie filtering seems to work well and in testing hasn't broken any web browsing. The underlying CookieMonster functions operate on cached copies in ram and are asynchronous to disk so there should be little or no measurable performance impact on browsing from cookies. localstorage deletion is not cached by any layer so, if enabled, might have some minor performance impact. Change-Id: I55c69292a5ddc460e0e50b340dc4330c28becc5e
Diffstat (limited to 'src/com/android/browser/BrowserBookmarksAdapter.java')
0 files changed, 0 insertions, 0 deletions