Confirmed users, Bureaucrats and Sysops emeriti
1,680
edits
NPAPI:ClearSiteData: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
|||
| Line 53: | Line 53: | ||
#define NPERR_MALFORMED_ORIGIN (NPERR_BASE + 16) | #define NPERR_MALFORMED_ORIGIN (NPERR_BASE + 16) | ||
</pre> | </pre> | ||
If site data is in use by an instance of the plugin when <code>NPP_ClearSiteData</code> is called then it is up to the plugin to do the right thing. | |||
= Open Issues = | = Open Issues = | ||
| Line 58: | Line 60: | ||
* Do we need a method for discovering what site data the plugin has? Mozilla and Apple have expressed a strong desire for this. | * Do we need a method for discovering what site data the plugin has? Mozilla and Apple have expressed a strong desire for this. | ||
* What is the syntax for an IPv6 address in site? As per RFC 3986 "IP-literal" ([http://greenbytes.de/tech/webdav/rfc3986.html#host.ip])? | * What is the syntax for an IPv6 address in site? As per RFC 3986 "IP-literal" ([http://greenbytes.de/tech/webdav/rfc3986.html#host.ip])? | ||
* What should be returned if a plugin does not support a requested type of data. What if it does not exist? What if clearing that data is not possible or simply not supported for any reason (data remains)? | * What should be returned if a plugin does not support a requested type of data. What if it does not exist? What if clearing that data is not possible or simply not supported for any reason (data remains)? | ||
* Make sure the requirements for parsing the origin argument are not too much of a burden for plugin developers. | * Make sure the requirements for parsing the origin argument are not too much of a burden for plugin developers. | ||