<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - Remove Unicode case-insensitive matching for usemap="""
href="https://bugs.webkit.org/show_bug.cgi?id=163894">163894</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Remove Unicode case-insensitive matching for usemap=""
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr>
<tr>
<th>Product</th>
<td>WebKit
</td>
</tr>
<tr>
<th>Version</th>
<td>Safari Technology Preview
</td>
</tr>
<tr>
<th>Hardware</th>
<td>Unspecified
</td>
</tr>
<tr>
<th>OS</th>
<td>Unspecified
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>Normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>P2
</td>
</tr>
<tr>
<th>Component</th>
<td>HTML DOM
</td>
</tr>
<tr>
<th>Assignee</th>
<td>webkit-unassigned@lists.webkit.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>d@domenic.me
</td>
</tr>
<tr>
<th>CC</th>
<td>cdumez@apple.com
</td>
</tr></table>
<p>
<div>
<pre>In <a href="https://github.com/whatwg/html/commit/6acdb2122298d2bb7bb839c0a61b4e1f9b0f9bc9">https://github.com/whatwg/html/commit/6acdb2122298d2bb7bb839c0a61b4e1f9b0f9bc9</a> we changed the HTML spec to remove all of its instances of "compatibility caseless" Unicode case-insensitive matching. There were three:
- <object usemap> matching <map name>
- <img usemap> matching <map name>
- radio button group names
All of these have been replaced with simple case-sensitive matching. WebKit already uses case-sensitive matching for radio button group names; see <a class="bz_bug_link
bz_status_NEW "
title="NEW - Radio button name is case sensitive"
href="show_bug.cgi?id=90617#c21">https://bugs.webkit.org/show_bug.cgi?id=90617#c21</a>. This bug is about the usemap cases.
We believe this change will be low-risk due to Chromium use counter data from the stable channel, which reveals that <0.0001% of pages have a map attribute that matches using ASCII case-insensitive matching, but not using case-sensitive mapping. Furthermore, zero additional matches are triggered by Chrome's Unicode case-insensitive matching. Another reason to believe this is low-risk is that the particular Unicode case-insensitive matching used was highly inconsistent and unreliable across browsers; the spec's "compatibility caseless" was fiction.
More background at <a href="https://github.com/whatwg/html/issues/1666">https://github.com/whatwg/html/issues/1666</a> and links contained therein. Web platform tests available at:
- <a href="http://w3c-test.org/html/semantics/embedded-content/the-img-element/usemap-casing.html">http://w3c-test.org/html/semantics/embedded-content/the-img-element/usemap-casing.html</a>
- <a href="http://w3c-test.org/html/semantics/embedded-content/the-object-element/usemap-casing.html">http://w3c-test.org/html/semantics/embedded-content/the-object-element/usemap-casing.html</a></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>