On Fri, Oct 23, 2009 at 10:38 AM, Drew <[email protected]> wrote:
>
> I've also found that you can use the canvas element method to work
> around this bug, since you can easily load an existing image into a
> canvas element.
Yup. In fact, that is exactly what setIcon({path...}) is doing
internally. See here:
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/renderer/resources/extension_process_bindings.js
(search for setIconCommon)
- a
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Chromium-extensions" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/chromium-extensions?hl=en
-~----------~----~----~----~------~----~------~--~---
