I wasn't suggesting you implement this in your NPAPI plugin. I was thinking of a monitor process, since you already have an installer. However, we have plans to provide uninstall hooks at some point, which should help here.
You should maybe star this bug to keep track of the progress: http://code.google.com/p/chromium/issues/detail?id=19383 On Tue, Jan 5, 2010 at 08:21, Aris <alexey.s.shish...@gmail.com> wrote: > Finnur, thank you again for your feedback! > > I’m going to use approach with accessing user’s preferences file, but > some questions still worry me. > > I’ll describe briefly what is my extension. It’s NPAPI extension > (plugin) with content script. I use a content script to > programmatically insert my plugin (scriptable object) into web pages. > I need access to window’s DOM during initialization of plugin. Later > on plugin is used to modify DOM. > > Now about accessing user’s preferences file. This approach assumes > that extension (my NPAPI dll) is always loaded (then I can read > preferences file during NP_Shutdown(…)) right after user launches > Chrome. So I can not use content script to programmatically insert my > plugin into web page, but instead I have to embed it into background > page: > > <embed type="application/x-my-extension" id="pluginId"> > > But I’m not sure if I can access window object from background page. > For example, I need access to window, document, > window.addEventListener to initialize plugin. Can I access these > objects from background page? > > Thank you in advance! > > > On Jan 4, 5:43 am, Finnur Thorarinsson <fin...@chromium.org> wrote: > > I think Alexey is asking for an event that gets triggered when the user > > manually installs an extension that was installed by Alexey's installer. > The > > event would trigger the Alexey's uninstaller to do some housekeeping. > > > > However, we don't have such an event to my knowledge. > > > > From the outside, I can only think of two indicators of an extension > being > > uninstalled. I'm not at my desk, so this is from memory: > > > > 1) The user's preferences file in the Chrome profile will either remove > the > > entry for the extension or mark it as uninstalled > > 2) The extension directory (see Mohamed's email) will get removed (don't > > remember if this happens immediately) > > > > Both of these are easy to test. > > > > The question in my mind is why you'd need to do this? Extensions don't > need > > to write to the Windows Installer database as a part of their > installation > > and as such don't need to cleanup after themselves. > > > > Is this so that a manual uninstall removes the extension Add/Remove > Programs > > entry (that you added during install) -- or is there another purpose? > > > > > > > > On Sun, Jan 3, 2010 at 14:40, Mohamed Mansour <m...@chromium.org> wrote: > > > Perhaps you can inform the user that they must close chrome browser > before > > > uninstalling. And your uninstall script will actually goto the users > "User > > > Data" directory and delete the extension folder which is just your > extension > > > id. > > > > > C:\Users\[user]\AppData\Local\Google\Chrome\User > > > Data\Default\Extensions\[extension-id] > > > > > -Mohamed Mansour > > > > > On Mon, Dec 28, 2009 at 7:52 AM, Aris <alexey.s.shish...@gmail.com> > wrote: > > > > >> Hello, All! > > >> We now distribute bunch of extensions for popular browsers, including > > >> Chrome, as part of Windows Installer package. A question that worries > > >> me is about our Chrome extension manual uninstalling - how can > > >> Windows installer be notified of uninstalling Chrome exetnsion > > >> manually from [Wrench menu] > Extensions? > > > > >> Details: > > >> What we need is a call to msiexec.exe with some parameters (stored in > > >> Windows registry upon installing; something like “msiexec /i > > >> [ProductCode] REMOVE=ChromePlugin /qb”) when user clicks button > > >> “Uninstall” on the chrome://extensions/ page – this removes Chrome > > >> extension entries from Windows Installer database. > > > > >> Google Chrome version: 4.0.266.0 > > >> Operating System: Windows XP Professional > > > > >> Thanks in advance! > > > > >> -- > > > > >> You received this message because you are subscribed to the Google > Groups > > >> "Chromium-extensions" group. > > >> To post to this group, send email to > chromium-extensions@googlegroups.com > > >> . > > >> To unsubscribe from this group, send email to > > >> chromium-extensions+unsubscr...@googlegroups.com<chromium-extensions%2bunsubscr...@googlegroups.com><chromium-extensions%2Bunsu > bscr...@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<chromium-extensions%2bunsubscr...@googlegroups.com><chromium-extensions%2Bunsu > bscr...@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<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.
