148
edits
Changes
→Current Proposal
= Current Proposal =
* Last modified: April 16May 27, 2010* Author: Julian Reschke (greenbytes), Dan Witte <dwitte@mozilla.com>
The current proposal is to add a new method, providing the new functionality:
<pre>
NPError NPN_ClearPrivacyDataNPN_ClearSiteData(
NPP instance,
PRUint64 flags, // what type of data to clear const char* sitedomain, // limit to sitedomain int PRUInt64 maxAge // max. age of information in seconds
);
</pre>
// can't clear by domain/site
#define NPERR_LIMITBYSITE_NOT_SUPPORTED (NPERR_BASE + nn)
// malformed 'domain' string
#define NPERR_MALFORMED_DOMAIN (NPERR_BASE + ll)
</pre>
Semantics:
* <code>flags</code> is a bitset representing which type(s) of data to clear; <code>0</code> means "clear all types".
* The <code>domain</code> argument is interpreted as follows:
** if a hostname of the form "foo.com", data in the "foo.com" domain and all subdomains should be cleared. In this form, <code>domain</code> must be a normalized ACE-encoded hostname, lowercased; must not contain a trailing dot; must not contain scheme, port, or other such fields; and must contain at least one embedded dot;
** if an IP address (either IPv4 or IPv6), data for that IP should be cleared;
** if <code>NULL</code>, all site-specific data and more generic data on browsing history (for instance, number of sites visited) should be cleared.
* <code>maxAge</code> is the maximum age of data to clear, inclusive, in seconds. If <code>maxAge</code> is <code>0</code>, no data is cleared. If <code>maxAge</code> is the maximum unsigned 64-bit integer, all data is cleared.
= Open Issues =
