> chrome.pageActions["my-page-action"].addListener(function(pageActionId,
replyData) {
> ...
> });
> This is useful if you have one handler that you want to hook up to
multiple page actions.
It used to be useful, back when we had multiple page actions all using one
event. Now you have a listener per pageActionId, so getting back the
pageActionId is not required anymore.
Should we use this opportunity to remove it?
-F
On Mon, Aug 31, 2009 at 04:40, Aaron Boodman <[email protected]> wrote:
> On Mon, Aug 31, 2009 at 4:35 AM, PhistucK <[email protected]> wrote:
>
>> Why should we specify the pageActionId twice...?
>>
>
> That isn't what that means. It means that you get passed the pageActionId
> as the input to the event handler:
>
> chrome.pageActions["my-page-action"].addListener(function(pageActionId,
> replyData) {
> ...
> });
>
> This is useful if you have one handler that you want to hook up to multiple
> page actions.
>
> - 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
-~----------~----~----~----~------~----~------~--~---
