[whatwg] MessageEvent and ports
Can someone explain why the postMessage() design exposes transfered ports both in .data and .ports? If that's a legacy artifact, can we call that out somewhere? (Asking around on IRC suggests it's an artifact that needs to be preserved by new variations of the postMessage() design, as e.g. seen in service workers. So the API remains somewhat consistent across variations. We might want to stipulate that too somehow.) -- https://annevankesteren.nl/
Re: [whatwg] MessageEvent and ports
On Fri, Mar 6, 2015 at 5:05 AM, Anne van Kesteren ann...@annevk.nl wrote: If that's a legacy artifact, can we call that out somewhere? Yes. It's a legacy artifact since before we had the generic concept of transferring and ports was this special one-off thing that you could stick in the second argument when postMessaging. / Jonas
