Bugzilla

This actually also applies to `window`. When it gets returned Chrome sends the following:

```

```

```
 0:24.99 pid:19354 1606986365627	RemoteAgent	TRACE	<-(connection {f59eee8f-0a6c-cb41-b781-b43d2cf4a8f8}) {"id":17,"sessionId":"2a9a26a4-636c-2841-9372-336f6f89912d","error":{"message":"Object is not serializable","data":"_serialize@chrome://remote/content/domains/content/runtime/ExecutionContext.jsm:533:13\n_toRemoteObjectByValue@chrome://remote/content/domains/content/runtime/ExecutionContext.jsm:510:24\ncallFunctionOn@chrome://remote/content/domains/content/runtime/ExecutionContext.jsm:268:21\ncallFunctionOn@chrome://remote/content/domains/content/Runtime.jsm:233:20\nexecute@chrome://remote/content/domains/DomainCache.jsm:99:25\nreceiveMessage@chrome://remote/content/sessions/ContentProcessSession.jsm:86:45\n"}}
```

This actually also applies to `window`. When it gets returned, Chrome sends the following:

```
{"type":"object","className":"Window","description":"Window","objectId":"{\"injectedScriptId\":1,\"id\":1}","preview":{"type":"object","description":"Window","overflow":true,"properties":[{"name":"parent","type":"object","value":"Window"}
```

Whereby in our case we completely fail to send the event from the content session to the TabSession. See bug 1680443.