Code: Select all
ReferenceError: TextEncoderStream is not defined[Learn More] sm24382728:1:325
Error: No stream found for single fetch decoding entry.client-slzaLiOH.js:16:57495
Stack trace:
te@https://resource.video.nimg.jp/web/scripts/nvpc_next/assets/typeof-3fvrxp9b.js:18:582
Jy@https://resource.video.nimg.jp/web/scripts/nvpc_next/assets/entry.client-slzaLiOH.js:26:904
wy@https://resource.video.nimg.jp/web/scripts/nvpc_next/assets/entry.client-slzaLiOH.js:26:2518
Bf@https://resource.video.nimg.jp/web/scripts/nvpc_next/assets/entry.client-slzaLiOH.js:16:34104
Ff@https://resource.video.nimg.jp/web/scripts/nvpc_next/assets/entry.client-slzaLiOH.js:16:61903
E1@https://resource.video.nimg.jp/web/scripts/nvpc_next/assets/entry.client-slzaLiOH.js:16:72397
k1@https://resource.video.nimg.jp/web/scripts/nvpc_next/assets/entry.client-slzaLiOH.js:16:106226
Us@https://resource.video.nimg.jp/web/scripts/nvpc_next/assets/entry.client-slzaLiOH.js:16:105327
Ac@https://resource.video.nimg.jp/web/scripts/nvpc_next/assets/entry.client-slzaLiOH.js:16:105165
L1@https://resource.video.nimg.jp/web/scripts/nvpc_next/assets/entry.client-slzaLiOH.js:16:102312
vv@https://resource.video.nimg.jp/web/scripts/nvpc_next/assets/entry.client-slzaLiOH.js:16:113593
Ea@https://resource.video.nimg.jp/web/scripts/nvpc_next/assets/entry.client-slzaLiOH.js:9:1657
As far as I can tell, this seems to be an interface that's part of the Encoding API. From the browser version compatibility tables listed there, I'm guessing PM probably has the non-stream interfaces implemented, and that these newer TextEncoderStream and TextDecoderStream interfaces are reliant upon the Streams API. I know PM is behind the current flavor of the Streams API spec because of UXP#2667, but I'm not competent enough to figure out if these encoding interfaces would work with PM's current Streams API implementation. Perhaps they might be relatively trivial to implement if their functionality is supposed to be analogous to the non-stream Encoding API interfaces?