I think this might be intentional (someone else please correct me if I'm
wrong).
In your popup, you can always use the messaging API to notify other
components in your extension, e.g.
Inside your popup page:
<script>
chrome.extension.connect().postMessage("page_action_popup");
</script>
Then inside your background (or other) page:
<script>
chrome.extension.onConnect.addListener(function(port) {
port.onMessage.addListener(function(message) {
if (message == "page_action_popup") {
console.log("page action popup clicked for tab " + port.tab.id);
}
});
});
</script>
On Wed, Nov 18, 2009 at 12:05 PM, SeRya <s.ryaza...@gmail.com> wrote:
> chrome.pageAction.onClicked (which could be used for it) stops firing
> when the popup specified in the manifest. Is it a bug?
>
> --
>
> 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...@googlegroups.com.
> To unsubscribe from this group, send email to
> chromium-extensions+unsubscr...@googlegroups.com<chromium-extensions%2bunsubscr...@googlegroups.com>
> .
> For more options, visit this group at
> http://groups.google.com/group/chromium-extensions?hl=en.
>
>
>
--
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...@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=.
