Bug 148871 - Indexing an object with an integer that is not a supported property index should not call the named property getter
Summary: Indexing an object with an integer that is not a supported property index sho...
Alias: None
Product: WebKit
Classification: Unclassified
Component: Forms (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Chris Dumez
URL: https://heycam.github.io/webidl/#idl-...
Keywords: InRadar
Depends on:
Reported: 2015-09-04 19:24 PDT by Ryosuke Niwa
Modified: 2016-01-28 10:31 PST (History)
8 users (show)

See Also:

Patch (7.00 KB, patch)
2015-10-24 16:23 PDT, Chris Dumez
no flags Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Ryosuke Niwa 2015-09-04 19:24:00 PDT
When an input element has a name which is an number, it should still be accessible via form.elements.
e.g. <input name="2"></input> should be accessible via form.elements[2].


This bug was found by the newly added test:
Comment 1 Radar WebKit Bug Importer 2015-09-04 19:24:27 PDT
Comment 2 Ryosuke Niwa 2015-09-04 19:25:29 PDT
Both Firefox and Chrome pass this test.
Comment 3 Chris Dumez 2015-10-23 16:14:11 PDT
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:

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:

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".
Comment 4 Chris Dumez 2015-10-23 16:16:58 PDT
Firefox and Chrome follow the Web IDL specification here.
Comment 5 Chris Dumez 2015-10-24 16:23:03 PDT
Created attachment 263986 [details]
Comment 7 WebKit Commit Bot 2015-10-26 11:09:36 PDT
Comment on attachment 263986 [details]

Clearing flags on attachment: 263986

Committed r191587: <http://trac.webkit.org/changeset/191587>
Comment 8 WebKit Commit Bot 2015-10-26 11:09:41 PDT
All reviewed patches have been landed.  Closing bug.