This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 17161 - There is no need to have legacycaller on HTMLPropertiesCollection
Summary: There is no need to have legacycaller on HTMLPropertiesCollection
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
Depends on:
Reported: 2012-05-23 13:49 UTC by contributor
Modified: 2012-08-24 19:31 UTC (History)
6 users (show)

See Also:


Description contributor 2012-05-23 13:49:49 UTC

There is no need to have legacycaller on HTMLPropertiesCollection

Posted from: by
User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:15.0) Gecko/15.0 Firefox/15.0a1
Comment 1 Boris Zbarsky 2012-05-23 13:50:43 UTC
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.
Comment 2 Philip J├Ągenstedt 2012-05-23 14:50:56 UTC
Opera supports"foo") as per spec, but I don't object to dropping it.
Comment 3 Philip J├Ągenstedt 2012-05-23 14:51:32 UTC
Discussion spawned from
Comment 4 David Zbarsky 2012-05-25 00:25:57 UTC
Also, PropertyNodeList doesn't need legacycaller, since NodeList no longer has legacycaller.
Comment 5 contributor 2012-07-18 17:38:31 UTC
This bug was cloned to create bug 18196 as part of operation convergence.
Comment 6 Ian 'Hixie' Hickson 2012-08-24 19:31:22 UTC

PropertyNodeList didn't have legacycaller, so I didn't change it.

Filed bug 18681 for test cases.
Comment 7 contributor 2012-08-24 19:31:32 UTC
Checked in as WHATWG revision r7268.
Check-in comment: Remove some 'legacycaller's