Thursday, June 21, 2012

Chrome Extensions: v2

So .... Google Chrome Extensions will soon require version 2 of manifest files and respective implementation.

I have my fairly complex Chrome Extension that makes use of several experimental/brand new HTML 5 technologies/tools: Drag&Drop, File API, Indexed DB, Canvas, etc...

Usually I keep an eye on the upcoming updates by having Chromium channel installed together with the stable Chrome release. I have this because certain implementations (ex: File API) are based on a draft spec, thus having the time to fix anything that might be modified before hit the stable release.

The last Chromium update caught me by surprise, I was expecting something to be broken as usual, I was not expecting that the manifest and some required implementations would be changed...

I find this gif to accurately express my face when I start reading the change log. I understand why they changed most of the stuff the way they did, but it has that feelling of "You must be joking" when I look at it...

Luckily for me, most of the stuff I did is compatible with the update, requiring just some touches in manifest file to make it work, though, those popup and options pages will suffer quite a few changes that make me shiver at the though of what I have to change and what else can get broken by it...

Even if I have no readers on my blog, if you made a Google Chrome Extension (or use one that might not have the best update support), take note:
http://code.google.com/chrome/extensions/manifestVersion.html
Look closely at that schedule support...

Good luck and happy coding :]