If you use messaging in your extension you cannot change to manifest version 2 without stranding users on older versions.manifest_version: 1 requires background_page to send messages.manifest_version: 2 explicitly disallows having background_page set.You currently cannot publish an extension that works in both version 1 and version 2.I have no idea why the developers decided to not include backwards compatibility between manifest_version 1 and manifest_version 2.I have a lot of upset users that are stuck with a broken extension because of this.
On Monday, July 9, 2012 9:51:58 AM UTC-5, Aaron Boodman wrote:
There's the "changes between 1 and 2" section on the bottom of this page:
http://code.google.com/chrome/extensions/manifestVersion.html
It's not a guide, but it lists all the things that change. The biggest
changes are the first two items: content_security_policy and
web_accessible_resources.
HTH,
- a
On Mon, Jul 9, 2012 at 2:35 AM, boxhead <andy....@gmail.com> wrote:
> I'm trying to upgrade my chrome extension from manifest version 1 to
> manifest version 2 but I can't find a migration guide, is there one?
>
> Cheers
>
> --
> You received this message because you are subscribed to the Google Groups
> "Chromium-extensions" group.
> To view this discussion on the web visit
> https://groups.google.com/a/chromium.org/d/msg/chromium-extensions/-/RDmTqgX86AUJ.
> To post to this group, send email to chromium-extensions@chromium.org.
> To unsubscribe from this group, send email to
> For more options, visit this group at
> http://groups.google.com/a/chromium.org/group/chromium-extensions/?hl=en.
--
You received this message because you are subscribed to the Google Groups "Chromium-extensions" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msg/chromium-extensions/-/UlpZBsFft_EJ.
Bjorn,
> For more options, visit this group at
> http://groups.google.com/a/chromium.org/group/chromium-extensions/?hl=en.
--
You received this message because you are subscribed to the Google Groups "Chromium-extensions" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msg/chromium-extensions/-/3Ooe1vGrpQEJ.
To post to this group, send email to chromium-...@chromium.org.
To unsubscribe from this group, send email to chromium-extens...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msg/chromium-extensions/-/3Ooe1vGrpQEJ.
+1 to the idea of including both manifest types. IMHO, that is the best solution since some people will inevitably end up stuck on older versions.
In addition, if Google wants to be able to force manifest_version 2 on us with no backward compatibility, it should first talk to the makers of popular chromium-based browsers about their update schedules. My brother, a RockMelt user, is already encountering extensions he can no longer use because of the manifest_version.
—Zachary “Gamer_Z.” Yaro
--
You received this message because you are subscribed to the Google Groups "Chromium-extensions" group.
To post to this group, send email to chromium-...@chromium.org.
To unsubscribe from this group, send email to chromium-extens...@chromium.org.
--
You received this message because you are subscribed to the Google Groups "Chromium-extensions" group.
To post to this group, send email to chromium-...@chromium.org.
To unsubscribe from this group, send email to chromium-extens...@chromium.org.
On Wed, Jul 25, 2012 at 12:33 AM, PhistucK <phis...@gmail.com> wrote:This isn't quite right. The "breaking changes" only apply if you opt
> Obviously, Chrome 19 had a significant bug in the area of backward
> compatibility when using both of the properties (background and
> background_page). But it was a major bug, obviously - not an intended
> behavior. Someone did not plan it the right way, this happens. Granted, you
> would expect more from Google, but we are human and we make mistakes. I am
> sure it was embarrassing for the planners as well.
>
> However, they rectified (although not fully, since Chrome 19 still exists
> somewhere and there is nothing they can do about it now) it in Chrome 20.
> Once they figured this problem exists (or even before), they immediately
> changed the documentation not to encourage developers to use the new
> manifest version yet, if I am not mistaking.
into manifest v2. Manifest v2 has existed since Chrome 18, but was
optional. We have been slowly ramping up its requiredness and recently
published our schedule for doing so:
http://code.google.com/chrome/extensions/manifestVersion.html
I personally think it is fine that these backward-incompatible changes were made, but then I think devs should be able to have separate manifest.json and manifest_v2.json files or something like that. Then older Chromium versions would ignore the v2 manifest and newer versions could use the highest available number they support.
—Zachary “Gamer_Z.” Yaro
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msg/chromium-extensions/-/Ih1mVGKLX1IJ.
To post to this group, send email to chromium-...@chromium.org.
To unsubscribe from this group, send email to chromium-extens...@chromium.org.
I feel like that is likely where we end up, similar to the way some Android apps have separate 1.x/2.x versions.
—Zachary “Gamer_Z.” Yaro
--
You received this message because you are subscribed to the Google Groups "Chromium-extensions" group.
There's the "changes between 1 and 2" section on the bottom of this page:
http://code.google.com/chrome/extensions/manifestVersion.html
It's not a guide, but it lists all the things that change. The biggest
changes are the first two items: content_security_policy and
web_accessible_resources.
HTH,
- a
On Mon, Jul 9, 2012 at 2:35 AM, boxhead <andy....@gmail.com> wrote:
> I'm trying to upgrade my chrome extension from manifest version 1 to
> manifest version 2 but I can't find a migration guide, is there one?
>
> Cheers
>
> --
> You received this message because you are subscribed to the Google Groups
> "Chromium-extensions" group.
> To view this discussion on the web visit
> https://groups.google.com/a/chromium.org/d/msg/chromium-extensions/-/RDmTqgX86AUJ.
> To post to this group, send email to chromium-...@chromium.org.
> To unsubscribe from this group, send email to
Hey. So I found this group after searching for a way to switch manifest versions. I'm not a developer nor a programmer, but I do have an extension that simply won't work. I'm positive this is the problem. The extension is a javascript file and as far as I know there is no json file to go with it. How would I make my extension work? I'm sorry to trouble you but I am in a bit of a pickle and I'm trying everything I can. I've attached to you the JS file. I attempted to just simply add "{...,"manifest_version": 2,...}"