Surma

Multiple workers should be absolutely fine. Not sure what is going wrong here. Can you create a minimal test case?

Can either of you provide me with a as-small-as-possible stylesheet that triggers this exception? As long a you don’t nest CQs inside MQs, it is _supposed_ to work, but there...

I’m not sure that this is a bug with Comlink, but rather worker-plugin, but it’s hard to tell from this. Can you put a test project in a gist or...

That should definitely be easy. I am now wondering if I should remove `createEndpoint` and put have it as a tree-shakeable `duplicateEndpoint` or something and add this one in instead...

Can you give me a small reproduction case in a gist or something where the results are different with the polyfill than with native CQs in Chrome Canary or something?

Interesting. Yeah that is possible. Do you mind writing a test/example that is a lot more reduced (for example without Comlink). The [`buffer-backed-object.test.js`](https://github.com/GoogleChromeLabs/buffer-backed-object/blob/e4911c3252e8f39ac50af2dcf389022ba315db8f/buffer-backed-object.test.js) file has a lot of examples.

Thanks for that! This was really helpful. So you are right. `ArrayOfBufferBackedObject` (AOBBO) creates an array full of proxies. The sorting works in that the _proxies_ are being reordered inside...

This will be solved with the [`Comlink.finalizer`](https://github.com/GoogleChromeLabs/comlink/pull/469/files#diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5R171) method once I finally land #469

Not yet. In general, ShadowDOM is not supported (I need to add that to the list!)

Updated the README. Gonna leave this open in case anyone has an idea how to handle ShadowDOM without doing something horrible.