This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/common-dom-interfaces.html Multipage: http://www.whatwg.org/C#htmloptionscollection-0 Complete: http://www.whatwg.org/c#htmloptionscollection-0 Comment: There is no need to have legacycaller on HTMLPropertiesCollection Posted from: 71.184.125.56 by bzbarsky@mit.edu User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:15.0) Gecko/15.0 Firefox/15.0a1
HTMLCollection no longer has legacycaller. So there is no reason to have it on HTMLPropertiesCollection, especially since there is no legacy behavior to be compatible with.
Opera supports elm.properties("foo") as per spec, but I don't object to dropping it.
Discussion spawned from https://bugzilla.mozilla.org/show_bug.cgi?id=591467
Also, PropertyNodeList doesn't need legacycaller, since NodeList no longer has legacycaller.
This bug was cloned to create bug 18196 as part of operation convergence.
Done. PropertyNodeList didn't have legacycaller, so I didn't change it. Filed bug 18681 for test cases.
Checked in as WHATWG revision r7268. Check-in comment: Remove some 'legacycaller's http://html5.org/tools/web-apps-tracker?from=7267&to=7268