<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body><span class="vcard"><a class="email" href="mailto:cdumez@apple.com" title="Chris Dumez <cdumez@apple.com>"> <span class="fn">Chris Dumez</span></a>
</span> changed
<a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - Indexing an object with an integer that is not a supported property index should not call the named property getter"
href="https://bugs.webkit.org/show_bug.cgi?id=148871">bug 148871</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;">Summary</td>
<td>form.elements should include elements whose name starts with a number
</td>
<td>Indexing an object with an integer that is not a supported property index should not call the named property getter
</td>
</tr>
<tr>
<td style="text-align:right;">URL</td>
<td>
</td>
<td>https://heycam.github.io/webidl/#idl-named-properties
</td>
</tr>
<tr>
<td style="text-align:right;">Status</td>
<td>NEW
</td>
<td>ASSIGNED
</td>
</tr>
<tr>
<td style="text-align:right;">Assignee</td>
<td>webkit-unassigned@lists.webkit.org
</td>
<td>cdumez@apple.com
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - Indexing an object with an integer that is not a supported property index should not call the named property getter"
href="https://bugs.webkit.org/show_bug.cgi?id=148871#c3">Comment # 3</a>
on <a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - Indexing an object with an integer that is not a supported property index should not call the named property getter"
href="https://bugs.webkit.org/show_bug.cgi?id=148871">bug 148871</a>
from <span class="vcard"><a class="email" href="mailto:cdumez@apple.com" title="Chris Dumez <cdumez@apple.com>"> <span class="fn">Chris Dumez</span></a>
</span></b>
<pre>Note
Note that if an indexed property getter or setter is specified using an operation with an identifier, then indexing an object with an integer that is not a supported property index does not necessarily elicit the same behavior as invoking the operation with that index. The actual behavior in this case is language binding specific.
In the ECMAScript language binding, a regular property lookup is done. For example, take the following IDL:
IDL
interface A {
getter DOMString toWord(unsigned long index);
};
Assume that an object implementing A has supported property indices in the range 0 ≤ index < 2. Also assume that toWord is defined to return its argument converted into an English word. The behavior when invoking the operation with an out of range index is different from indexing the object directly:
ECMAScript
var a = getA();
a.toWord(0); // Evalautes to "zero".
a[0]; // Also evaluates to "zero".
a.toWord(5); // Evaluates to "five".
a[5]; // Evaluates to undefined, since there is no property "5".</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>