So, the *iconIndex* approach to setting page action icons is going away. The latest trunk build allows you to specify an optional *default_icon*(relative path to a file within your extension) and programmatically change it using *setIcon*. You specify a *tabId *(for the tab you want to change the icon in) and either a *path* (same as *default_icon*) or *imageData, which is described as*: "Pixel data for an image. Must be an ImageData object (for example, from a canvas element)."
The only caveat I can think of is that I *think *the latest dev release was delayed so maybe the dev release that is most current doesn't support this yet, but you could give it a try. If it doesn't work, you can also download the latest trunk build to test this on here: http://build.chromium.org/buildbot/continuous/LATEST/chrome-win32.zip ... or just wait until we release the new dev build. :) -F On Wed, Nov 4, 2009 at 02:11, Teo [GD API Guru] <teomina...@gmail.com>wrote: > > Hi, > > what would be the right way of using the canvas in this case? Do we > define it in background.html or in manifest.json... (I'm especially > interested in what i need to pass as the 'iconId' parameter of > 'enableForTab'). > > Thanks, > Teo > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-extensions" group. To post to this group, send email to chromium-extensions@googlegroups.com To unsubscribe from this group, send email to chromium-extensions+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/chromium-extensions?hl=en -~----------~----~----~----~------~----~------~--~---
