<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body><span class="vcard"><a class="email" href="mailto:ilatypov@infradead.org" title="Ilguiz Latypov <ilatypov@infradead.org>"> <span class="fn">Ilguiz Latypov</span></a>
</span> changed
<a class="bz_bug_link
bz_status_NEW "
title="NEW - Accessing form.action as property URI-encodes spaces but not curly braces"
href="https://bugs.webkit.org/show_bug.cgi?id=157153">bug 157153</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">CC</td>
<td>
</td>
<td>ilatypov@infradead.org
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Accessing form.action as property URI-encodes spaces but not curly braces"
href="https://bugs.webkit.org/show_bug.cgi?id=157153#c4">Comment # 4</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Accessing form.action as property URI-encodes spaces but not curly braces"
href="https://bugs.webkit.org/show_bug.cgi?id=157153">bug 157153</a>
from <span class="vcard"><a class="email" href="mailto:ilatypov@infradead.org" title="Ilguiz Latypov <ilatypov@infradead.org>"> <span class="fn">Ilguiz Latypov</span></a>
</span></b>
<pre>I think of a URL as a string that needs parsing before obtaining its values. Both the encoded and the raw curly brace would unambiguously reduce to the raw curly brace after decoding the URL. I understand the advantage of the approach "accept liberally, output conservatively" in terms of the browser presenting DOM elements to Javascript, so the suggested correction makes sense to me.
I see that RFC 3986, while formally calling for encoding any character outside the following characters,
ALPHA / DIGIT / "-" / "." / "_" / "~"
/ "!" / "$" / "&" / "'" / "(" / ")" / "*" / "+" / "," / ";" / "="
/ ":" / "@"
suggests that "it is sometimes better for usability to avoid percent-encoding" special characters. These two parts of the RFC look self-contradictory.
As for <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - Freeze when loading a particular page on washingtonpost.com with NetworkProcess enabled"
href="show_bug.cgi?id=116887">bug 116887</a>, I obtained the same response from Washington Post regardless of the encoding, and I interpret this as an early conservative output. Perhaps, the server did produce different results a few years back, and the conservative output of the browser on sending the request could work that around.</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>