<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [Fetch API] Ensure correct behavior when passing null and undefined to construct Headers from its constructor or from Request/Response constructors"
href="https://bugs.webkit.org/show_bug.cgi?id=168153#c1">Comment # 1</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [Fetch API] Ensure correct behavior when passing null and undefined to construct Headers from its constructor or from Request/Response constructors"
href="https://bugs.webkit.org/show_bug.cgi?id=168153">bug 168153</a>
from <span class="vcard"><a class="email" href="mailto:youennf@gmail.com" title="youenn fablet <youennf@gmail.com>"> <span class="fn">youenn fablet</span></a>
</span></b>
<pre>After <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - [Fetch API] fetch fails when undefined is passed as headers"
href="show_bug.cgi?id=168043">bug 168043</a>, fetch implementation is more consistent with fetch spec prior the introduction of Record in HeadersInit.
We should further strive to align with the spec in that area.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>