Is this a joke? Because if it is, it is really a bad one. Where do you get
these ideas from?
1. You are punching your breasts with your fists saying you are working for
securing the extensions (like killing eval and splitting the extensions
scripts in 3 independent worlds which can exchange information via DOM or
messages), yet you add the most insecure element as being the main
instrument of persistence. Great thinking!
2. The DOM connection in between the background (event) page and its popup
counterpart will just be killed in a periodical check (or longer period of
activity, for that matter) because the background (event) page will be
destroyed due to inactivity. Again, great thinking!
If you really want to see no extensions in your great browser, just say it
so and don't bring this kind of arguments.
A very unhappy extension developer,
On Mon, Aug 27, 2012 at 10:33 PM, Aaron Boodman <a...
> *Hello extension developers!
> In Chrome 22, we’re releasing two new APIs that we hope you’ll use to kill
> off your memory-guzzling background pages<http://blog.chromium.org/2012/06/put-your-extensions-on-diet-with-eve...>
> - Event pages<http://developer.chrome.com/beta/extensions/event_pages.html>are a replacement for background pages. They are similar to background
> pages, except that they are automatically destroyed by the system when
> idle, and brought back to life when needed. Converting to event pages is
> usually really easy<http://developer.chrome.com/beta/extensions/event_pages.html#transition>,
> and will improve Chrome’s performance and responsiveness -- especially on
> lower-power devices.
> - The Storage API<http://developer.chrome.com/beta/extensions/storage.html>is a replacement for HTML5’s localStorage, but with a couple big
> advantages. The Storage API can be used within content scripts directly,
> without having to send messages to a background page. This should allow
> many extensions to completely remove their background pages. The Storage
> API also has built-in support for synchronization. Any data stored within
> the sync namespace<http://developer.chrome.com/beta/extensions/storage.html#property-sync>is automatically replicated to each device the user has your extension
> installed on.
> To add some extra incentive, we’ll be featuring the awesomest extensions
> that kill their background pages using either of these APIs in the Chrome
> Web Store. Featured extensions periodically show up at the top of the extensions
> category <https://chrome.google.com/webstore/category/extensions>, with
> gigantic promotional images that are pretty much impossible to miss. We'll
> also be selecting a few of these extensions to showcase in an upcoming blog
> post. To be eligible, just upload your converted, background-page-free
> extension to the Chrome Web Store by October 1.*
> *Note that both these new APIs require manifest version 2<http://developer.chrome.com/extensions/manifestVersion.html>.
> We plan to require manifest v2 for updates to all existing extensions
> starting in Chrome 23, so this is a good thing to start looking at now
> So get out your editor and a scalpel, and let us know how these APIs work
> for you. If you have any questions, just reply to this message, or start a
> new thread on the mailing list.
> Happy hacking,
> - Ben (storage), Matt (event pages), Yoyo (event pages), and Aaron
> You received this message because you are subscribed to the Google Groups
> "Chromium-extensions" group.
> To post to this group, send email to chromium-extensi...@chromium.org.
> To unsubscribe from this group, send email to
> For more options, visit this group at