<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Decode data URLs in web process"
href="https://bugs.webkit.org/show_bug.cgi?id=148128#c21">Comment # 21</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Decode data URLs in web process"
href="https://bugs.webkit.org/show_bug.cgi?id=148128">bug 148128</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>(In reply to <a href="show_bug.cgi?id=148128#c20">comment #20</a>)
<span class="quote">> We need to do something along these lines because data urls expect bytes to
> get through unmodified even when not using base64. This kind of stuff is
> supposed to work:
>
> data:image/png,%89PNG%0D%0A%1A%0A%00%00%00%0D...</span >
Yes, there’s no question that for data URLs we want to decode into bytes, not characters. I think it's a bit peculiar that we decode into a String rather than a SharedBuffer or something like that.
My point was about the other callers of this API, not a doubt that this was correct for data URL handling.</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>