I agree that the name should be something like chrome_min_version. I understand that it's unrealistic to change the name in Omaha, but maybe auto-update could support both, so it's at least consistent for people who don't use Omaha? -Nick
On Mon, Oct 12, 2009 at 3:11 PM, Antony Sargent <[email protected]>wrote: > There is no such mechanism today, but as Nick says this might make sense. > Can you enter a bug at crbug.com/new so we don't forget about it, and can > prioritize against other work? > As an aside, I'm not crazy about the name "prodversionmin" since it's a > little confusing *which* version we're talking about, but that's what Omaha > already uses. I'd prefer something like "chrome_min_version" or > "browser_min_version", but it might be weird to have a different name in the > extension manifest from the autoupdate manifest. > > > On Fri, Oct 9, 2009 at 3:29 PM, Colin Bleckner <[email protected]> wrote: > >> >> The auto-update file allows extension developers to specify a >> prodversionmin flag that will only an extension if the user is running a >> specified minimum version of Chrome. I'd love to be able to set a >> similar flag in the manifest.json file too, but I don't see anything in >> the documentation. Is this a hidden (or planned) feature? >> >> Colin >> >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
