Open Bug 1796307 Opened 2 years ago Updated 1 years ago

browsingData WebExtension API support

Categories

(Fenix :: WebExtensions, enhancement)

All
Android
enhancement

Tracking

(Not tracked)

People

(Reporter: gl, Unassigned)

References

Details

(Whiteboard: [addons-jira])

From github: https://github.com/mozilla-mobile/android-components/issues/8937.

Once GeckoView support lands https://bugzilla.mozilla.org/show_bug.cgi?id=1625233 AC will be able to implement the browsingData WebExtension API, the provisional GV API is as follows:

public interface BrowsingDataDelegate {
    GeckoResult<Settings> onGetSettings();
    GeckoResult<Void> onClearFormData(final long sinceUnixTimestamp);
    GeckoResult<Void> onClearPasswords(final long sinceUnixTimestamp);
    GeckoResult<Void> onClearDownloads(final long sinceUnixTimestamp);
    GeckoResult<Void> onClearHistory(final long sinceUnixTimestamp);
}

Where onGetSettings gets the default settings for what data is deleted by default when pressing the "Clear Data" button in the browser UI, e.g. history, cookies, etc.

And the onClearX are callbacks that indicate that the browser should delete all X created since the timestamp passed in, e.g. onClearDownloads should remove all downloads create before the timestamp passed in.

Note: currently onClearFormData will be a no-op because the browser doesn't store any form data (until we will start storing Credit Cards and addresses information).

┆Issue is synchronized with this Jira Task

Change performed by the Move to Bugzilla add-on.

For forward-compatibility, consider including a parameter to clear by host names (e.g. clearing downloads by hostname - bug 1643917).

We'd need a consistent definition for that though... (bug 1797376)

The severity field is not set for this bug.
:cpeterson, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(cpeterson)
Severity: -- → N/A
Type: defect → enhancement
Whiteboard: [addons-jira]
Flags: needinfo?(cpeterson)
You need to log in before you can comment on or make changes to this bug.