Confirmed users, Bureaucrats and Sysops emeriti
1,680
edits
NPAPI:ClearSiteData: Difference between revisions
Jump to navigation
Jump to search
→Open Issues
No edit summary |
|||
| Line 60: | Line 60: | ||
* 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])? | ||
* Make sure this API allows for a "forget about this site" UI, which Firefox has. | * Make sure this API allows for a "forget about this site" UI, which Firefox has. | ||
* Do we need a method for discovering what site data the plugin has? Mozilla and Apple have expressed a strong desire for this. | |||
* If NPP_ClearSiteData is called while there is a plug-in instance that is actively using some of the targeted local data, what should happen? | |||
* 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. | |||
* Suggested that we document what happens when a particular plug-in is keyed by domain, not origin. This way for simplicity purposes the API can handle both models, regardless of how it's keyed. The specific suggestion is that for a plug-in that stores domain-keyed info, that plug-in will just strip the protocol and (optional) port. | |||
= Notes = | = Notes = | ||