[extension API] messaging flow #143

Closed
paulirish opened this Issue Aug 19, 2014 · 1 comment

Comments

Projects
None yet
1 participant
@paulirish
Member

paulirish commented Aug 19, 2014

https://developer.chrome.com/extensions/devtools has great overview of communicating between the various pieces, but it's still a little incomplete.

One tricky area is passing messages from a contentscript back into a devtools panel.

There's no direct connectivity between the page being inspected and DevTools extension panels -- we usually recommend this flow: DOM messaging from the injected inspected page code to the content script, then extension messaging to send that to the background page and the front-end iframe.

Example: polymer extension message passing via CustomEvent on the window

another option is: buffering events in inspected page and polling them

@paulirish paulirish changed the title from devtools extension API messaging flow to [extension API] messaging flow Jan 6, 2015

@paulirish

This comment has been minimized.

Show comment
Hide comment
@paulirish

paulirish Jan 6, 2015

Member

covered in real docs thanks to thomas boyt's patch
https://codereview.chromium.org/632793002

Member

paulirish commented Jan 6, 2015

covered in real docs thanks to thomas boyt's patch
https://codereview.chromium.org/632793002

@paulirish paulirish closed this Jan 6, 2015

@pajtai pajtai referenced this issue in Duder-onomy/app-state-chrome-extension Jan 1, 2016

Closed

Two way binding for the appState #1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment