It was designed this way intentionally, though I agree with you that in the case of manual installation, it is counter-intuitive.
There is an edge case that I can't remember right now that we were concerned about that made us do it this way. Erik will remember... - a On Fri, Oct 30, 2009 at 9:27 AM, Antony Sargent <[email protected]> wrote: > I'm pretty sure we intentionally designed it this way but I can't remember > off the top of my head what the concern was. Perhaps one of the other > extension devs will recall. > > On Fri, Oct 30, 2009 at 8:44 AM, Robert Billingslea > <[email protected]> wrote: >> >> I took a quick look through crbug.com for this issue but I didn't see an >> existing change request that matched. >> I am not sure if this was intentional, but if an extension exists with a >> particular version and you manually try to reinstall an updated crx (with >> the same version), it doesn't appear to update any of the files. >> There have been times (such as when the chrome dev channel updates and >> breaks our extension or when debugging a problem with a user) that we may >> want to push out a quick chrome build without a version bump (we have many >> products that share the same version and do not want to make new builds >> every week because the new chrome dev build has issues, it is much easier to >> tell the early chrome early adopters to redownload the crx). >> I think most people would expect it to replace the current version. >> Thanks, >> Bob >> > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-extensions" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/chromium-extensions?hl=en -~----------~----~----~----~------~----~------~--~---
