Re: [whatwg/streams] How much latitude should implementations have in looking up transformer.transform()? (#691)

> Oh, and also, we use the same pattern for custom elements. Here was the thread with arguments for it at that time: w3c/webcomponents#417

That's a good discussion of the up- and downsides to this, thanks. I don't know if the same is true for custom elements, though I'd assume so, but as I said above the important part for me is that having this check be required would necessitate entering the JS engine in *some* fashion, even if it doesn't necessarily entail running JS code itself. (Though recommending developers freeze the object or make the `transform` property non-configurable would also work.)

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/streams/issues/691#issuecomment-285691016