<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - URL paths should not be normalized when encoded"
href="https://bugs.webkit.org/show_bug.cgi?id=144320#c6">Comment # 6</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - URL paths should not be normalized when encoded"
href="https://bugs.webkit.org/show_bug.cgi?id=144320">bug 144320</a>
from <span class="vcard"><a class="email" href="mailto:darin@apple.com" title="Darin Adler <darin@apple.com>"> <span class="fn">Darin Adler</span></a>
</span></b>
<pre>So I think we have two questions:
1) If we did want to make normalization separate, what is a good idiom that would keep things brief and efficient and just use the StringView as-is without memory allocation when no normalization is needed?
2) Is normalization helpful for all those other clients?
I suppose we can leave it inside encode for now, but we should make sure that all those other call sites want normalization and have someone write test cases for them.</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>