I'm seeing issues on IE with a fetch polyfill that I think are due to the change in 11d14fc642f4878e9dc8e2329a62e7a8d18895fe.
Basically, headers is getting passed to fetch as an array of arrays, and the implementation is expecting that the forEach callback will be called with value, name.
typedef (sequence<sequence> or record<ByteString, ByteString>) HeadersInit
So I'm guessing that this is an issue with the polyfill instead of this module. But I'm curious if you can give some background on 11d14fc642f4878e9dc8e2329a62e7a8d18895fe.
I'm seeing issues on IE with a fetch polyfill that I think are due to the change in 11d14fc642f4878e9dc8e2329a62e7a8d18895fe.
Basically,
headers
is getting passed tofetch
as an array of arrays, and the implementation is expecting that theforEach
callback will be called withvalue, name
.The MDN docs suggest that the
headers
property isI think the spec says that the
headers
property can be an array of arraysSo I'm guessing that this is an issue with the polyfill instead of this module. But I'm curious if you can give some background on 11d14fc642f4878e9dc8e2329a62e7a8d18895fe.