browserAction.setIcon and pageAction.setIcon can both optionally accept ImageData objects. Since those objects can't be structured cloned via the message manager, we need to deal with them somehow. The obvious possibilities are: 1) Update the message manager's structured clone algorithm to support cloning ImageData objects. Since we already have code to handle this for DOM structured clone, it should be pretty doable. 2) Post-process the objects from the schema code, and convert them to data: URLs before passing them to the API methods, rather than after, as we do now.
a year ago
Assignee: nobody → kmaglione+bmo
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.