- From: Domenic Denicola <notifications@github.com>
- Date: Fri, 10 Mar 2017 06:18:29 -0800
- To: whatwg/streams <streams@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 10 March 2017 14:19:03 UTC
> If the objects passed to Stream constructors behave differently from Javascript objects in other contexts then we're going against our own design philosophy. I guess I'm not as conflicted because even though they behave differently, it's really not a big deal in practice. I've never really seen JavaScript code that dynamically changes the methods of an object passed elsewhere and expects that to be respected---even though it's probably the case that doing so would work, since most object-accepting code will use `foo.bar()` instead of `previouslySavedBar.call(foo)`. Oh, and also, we use the same pattern for custom elements. Here was the thread with arguments for it at that time: https://github.com/w3c/webcomponents/issues/417 -- 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-285679821
Received on Friday, 10 March 2017 14:19:03 UTC