Confirmed users
512
edits
Electrolysis/Jetpack: Difference between revisions
Jump to navigation
Jump to search
m
Clarifications about existing CPOW limitations
m (Add clarification) |
m (Clarifications about existing CPOW limitations) |
||
| Line 48: | Line 48: | ||
} | } | ||
In either instance, the chrome process will end up calling the CPOW callback using a CPOW document object (assuming content processes exist). | In either instance, the chrome process will end up calling the Jetpack CPOW callback using a content CPOW document object (assuming content processes exist). | ||
Note that the solutions as described are currently un-implementable, because there's no way to pass | Note that the solutions as described are currently un-implementable for certain circumstances, because there's no way to pass chrome objects to the CPOW callback as a parameter. We need reverse (chrome -> jetpack) CPOWs for that to work, and they don't exist yet. | ||
The upside is that jQuery should Just Work as soon as the chrome -> jetpack CPOWs do exist. | The upside is that jQuery should Just Work as soon as the chrome -> jetpack CPOWs do exist. | ||