Add an API to manage local data (cookies, local storage, app cache, indexed DB and web DB)

Bug #1260014 reported by Olivier Tilloy
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Oxide
Medium
Unassigned
webbrowser-app (Ubuntu)
Undecided
Olivier Tilloy

Bug Description

A modern browser application should offer as an advanced feature a way to manage cookies (list them, selectively delete some, clear all). Oxide needs to expose such an API.

Related branches

Changed in oxide:
assignee: nobody → Alexandre Abreu (abreu-alexandre)
Changed in oxide:
importance: Undecided → Medium
status: New → Triaged
summary: - Add an API to manage cookies
+ Add an API to manage local data (cookies, local storage, app cache,
+ indexed DB and web DB)
Revision history for this message
Alberto Mardegan (mardy) wrote :

Here's a couple of important use-cases for being able to read browser cookies:
- Transfer cookies from the Browser app to the webapp container
- Transfer cookies from Online Accounts to the webapp container

We are currently experimenting with reading the cookies straight from the SQLite database, but we find that they aren't always on sync. At the very least, we'd need to have a way to trigger the flush of the cookies to the DB.

Revision history for this message
Bill Filler (bfiller) wrote :

Can we prioritize adding an API to clear disk cache first? This is really needed in devices like krillin where the disk space is extremely limited. Clearing cookies would be the second priority in my opinion.

Olivier Tilloy (osomon)
Changed in oxide:
assignee: Alexandre Abreu (abreu-alexandre) → Olivier Tilloy (osomon)
Olivier Tilloy (osomon)
Changed in oxide:
status: Triaged → In Progress
milestone: none → branch-1.6
Revision history for this message
Olivier Tilloy (osomon) wrote :

From IRC discussion today:

 <chrisccoulson> The kind of API I'd like to see is something like clearSiteData(flags, origin, time), where flags is a bitwise OR of things like app cache, cookies, local storage etc and time specifies how far back in history to delete
 <chrisccoulson> although, specifying an origin probably wouldn't be appropriate for all types of storage
 <chrisccoulson> It would also need a way for an application to track progress - ie, clearSiteData() would return an object with a completed signal or something
 <chrisccoulson> Of course, my API idea might not make sense either - particularly if there are lots of storage types in Chromium that we don't have such control over

Changed in oxide:
milestone: branch-1.6 → branch-1.7
status: In Progress → Confirmed
status: Confirmed → Triaged
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package webbrowser-app - 0.23+15.04.20150408-0ubuntu1

---------------
webbrowser-app (0.23+15.04.20150408-0ubuntu1) vivid; urgency=medium

  [ CI Train Bot ]
  * New rebuild forced.
  * Resync trunk.

  [ Olivier Tilloy ]
  * Add a "Clear Cache" entry under the privacy settings. (LP: #1296364,
    #1260014)
  * Add settings page, per design specification. This adds qml-module-
    qt-labs-folderlistmodel and qml-module-qt-labs-settings as runtime
    dependencies for webbrowser-app. (LP: #1351183)
  * Autopilot tests for the settings UI. added:
    tests/autopilot/webbrowser_app/tests/test_settings.py

  [ Riccardo Padovani ]
  * Add settings page, per design specification. This adds qml-module-
    qt-labs-folderlistmodel and qml-module-qt-labs-settings as runtime
    dependencies for webbrowser-app. (LP: #1351183)
  * Add settings page, per design specification. This adds qml-module-
    qt-labs-folderlistmodel and qml-module-qt-labs-settings as runtime
    dependencies for webbrowser-app. (LP: #1351183)
 -- CI Train Bot <email address hidden> Wed, 08 Apr 2015 14:09:36 +0000

Changed in webbrowser-app (Ubuntu):
status: New → Fix Released
Olivier Tilloy (osomon)
Changed in webbrowser-app (Ubuntu):
assignee: nobody → Olivier Tilloy (osomon)
Changed in oxide:
milestone: branch-1.7 → branch-1.8
Olivier Tilloy (osomon)
Changed in oxide:
milestone: branch-1.8 → branch-1.9
Changed in oxide:
milestone: branch-1.9 → branch-1.11
Changed in oxide:
milestone: branch-1.11 → branch-1.12
Changed in oxide:
milestone: branch-1.12 → branch-1.13
Changed in oxide:
milestone: branch-1.13 → branch-1.14
Changed in oxide:
milestone: branch-1.14 → none
Revision history for this message
Olivier Tilloy (osomon) wrote :

This is implemented as BrowsingDataRemover in chrome (chrome/browser/browsing_data/browsing_data_remover.h).

Revision history for this message
Olivier Tilloy (osomon) wrote :

Another important use case is autofill profiles (see bug #1214048).

description: updated
Revision history for this message
Chris Coulson (chrisccoulson) wrote :

This is separate from autofill profiles, but will be necessary to clear site-specific autocomplete data.

Olivier Tilloy (osomon)
Changed in oxide:
assignee: Olivier Tilloy (osomon) → nobody
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Related blueprints