Re: [whatwg/encoding] Make TextEncoder and TextDecoder be transform streams (#127)

I think a problem here is that if a script running in a document invokes the constructor of either `TextDecoder` or `TextEncoder` in an `<iframe>` element the tear-off transform-related objects will have the associated global of the document (the current global/realm) and not the `<iframe>`'s document.

See also https://www.w3.org/Bugs/Public/show_bug.cgi?id=24652 and https://w3c-test.org/WebIDL/current-realm.html.

Note that if you change it to accept a DOMString you also need to do conversions from [code unit](https://infra.spec.whatwg.org/#code-unit) to [scalar value](https://infra.spec.whatwg.org/#scalar-value) (you probably meant that; stating it here so I don't forget to verify it).

(Tests can use JavaScript features that ship in the latest release of all browsers. At least, that's my rule of thumb.)

-- 
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/encoding/pull/127#issuecomment-351362426