http://bugs.winehq.org/show_bug.cgi?id=29387
Qian Hong fracting@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID
--- Comment #2 from Qian Hong fracting@gmail.com 2012-01-26 11:13:17 CST --- Sorry, this report is invalid, my bad:
1. In chrome/common/extensions/extensions.cc: --- snip --- if (flags & REQUIRE_MODERN_MANIFEST_VERSION && manifest_version() < kModernManifestVersion && !CommandLine::ForCurrentProcess()->HasSwitch( switches::kAllowLegacyExtensionManifests)) { *error = ASCIIToUTF16(errors::kInvalidManifestVersion); return false; } --- snip ---
In chrome/common/extensions/extension_constants.cc: --- snip --- const char kInvalidManifestVersion[] = "The 'manifest_version' key must be present and set to 2 (without quotes)."; --- snip ---
The new chromium browser requires a new extension manifest file, this error is by design.
In chrome/common/chrome_switches.cc: --- snip --- const char kAllowLegacyExtensionManifests[] = "allow-legacy-extension-manifests"; --- snip ---
A "--allow-legacy-extension-manifests" switcher could avoid this error
2. Same behaviors on Windows with same chromium version.