Antony, I agree that oninstall would be sufficient to handle the corrupt data case. However, I think onuninstall is important for NPAPI extensions, who otherwise have no chance to clean up the system (and we don't know what changes they've made, so we can't do it for them).
http://code.google.com/p/chromium/issues/detail?id=19383 What abuse do you have in mind? -Nick On Thu, Nov 26, 2009 at 4:50 PM, Akira <ak...@yayakoshi.net> wrote: > I would not want extension data to be deleted by default. Definitely > many users will uninstall extensions if they're trying to debug a > mysterious symptom (potentially not even caused by any extension) and > then re-install. I know in the case of my extension they'll lose a lot > small stored details that would make using it again frustrating. > > A prompt to optionally the delete the data on uninstall would cover > the bases. If an oninstall hook could be applied then even better > handling of a corrupted data situation can be programmed by the > developer. > > Akira > > -- > > You received this message because you are subscribed to the Google Groups > "Chromium-extensions" group. > To post to this group, send email to chromium-extensi...@googlegroups.com. > To unsubscribe from this group, send email to > chromium-extensions+unsubscr...@googlegroups.com<chromium-extensions%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/chromium-extensions?hl=en. > > > -- You received this message because you are subscribed to the Google Groups "Chromium-extensions" group. To post to this group, send email to chromium-extensi...@googlegroups.com. To unsubscribe from this group, send email to chromium-extensions+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/chromium-extensions?hl=en.
