Confirm, emeritus
1,680
edits
Changes
no edit summary
/* More flags may be defined later, this spec will be updated. */
</pre>
* The <code>site</code> argument is interpreted as follows: ** The preferred form for this argument is an origin: scheme + "://" + domain + optional port preceded by ":" (e.g. "http://mozilla.org:80").** If a hostname of the form "foo.com", data in the "foo.com" domain and all subdomains should be cleared. In this form domains must be in lowercase normalized ACE-encoded form, they must not contain a trailing dot, must not contain a 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.** If <code>!NULL</code>, argument is a domain per the domain portion of the URI specification but with a requirement for NFKC-normalized UTF-8 encoding. No other encoding is allowed. All sub-domains of the specified domain are to be cleared as well. If a sub-domain is specified only it and its sub-domains are to be cleared. For example, if a browser specifies "b.a.com" then data for "b.a.com" and "c.b.a.com" is to be cleared but data for "a.com" is not to be cleared.
* The <code>maxAge</code> argument is the maximum age in seconds of data to clear, inclusive. 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.
* Make sure the requirements for parsing the origin argument are not too much of a burden for plugin developers.
* Do we need a method for discovering what site data the plugin has? Mozilla and Apple have expressed a strong desire for this.
= Notes =
