1370884 - postMessage throws DataCloneError: The object could not be cloned.

Status: RESOLVED WONTFIX

(WebExtensions :: General, defect)

Description

[Anthony Maton [:anthony]]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36

Steps to reproduce:

I tried to send an Object through a port using postMessage({}).

The object is structured like this

{
   "desc": "some_description",
   "name": "some_name",
   "errors": [{"msg": "article_length_info", "msgParams": ["317","1"], "type":3}]
}

With more or less element in the table.




Actual results:

An error is returned : DataCloneError: The object could not be cloned.


Expected results:

The object should have been transferred without any hassle. It was working yesterday (6th of June 2017) on Nightly, so I guess some patch broke it during the night.

Comment 1

[Kris Maglione [:kmag]]

Can you please attach a testcase add-on that shows the problem?

Comment 2

[Anthony Maton [:anthony]]

Attachment: Webextension triggering the issue

This is not really test case but it triggers the issue. 
I'll try to reduce it to a minimal use case.

Comment 3

[Kris Maglione [:kmag]]

It looks like you're trying to send an object that contains a function property. We used to (accidentally) ignore those properties as a byproduct of the cloning being done through security wrappers, but they were never supported.