javascript - Problems crossing the boundary between protected greasemonkey execution space and the unsafeWindow land -

Here's my problem: I have registered some callback in Yahoo event-driven webpage (betfair.com market idea)

So far it is so simple.

The next step is to get this incident back into the Grasinaki land, and when I know that from Graysmani's place you can call unsafe Window.stuff, there is no reverse operation (by design) .

So if I happen to event material, a cometd queue, my carefully installed jquery, greasemonkey, YUI2, Betfair environment telling me that unsafe fails the window process cant call GM_ajax stuff. It is clearly safe and sensible, but it basically prevents me from doing what I want to do.

Has anyone tried to do this (ignore cometd content, only general ajax call) and successful?

I have taken a look at these pages: But it does not work for all calls.

This does not seem obvious to me addEventListener () , preventDefault () , stopPropagation () , etc.? Why can not GM be trapped by the end?

Anyway, worst situation, can not you do anything like that?

1. A hidden IFrame, Div, or whatever, GM has monitored it for DOM changes. / Li>
2. Type the captured event information in that node.
3. Then grasimaki parses the data and uses GM_ajax as you see fit.