18196 2012-07-18 17:38:27 +0000 There is no need to have legacycaller on HTMLPropertiesCollection 2012-09-21 10:22:00 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#htmloptionscollection-0 P3 normal --- 1 contributor silviapfeiffer1 bzbarsky dzbarsky mike philipj public-html-admin public-html-wg-issue-tracking robin public-html-bugzilla oldest_to_newest 70858 0 contributor 2012-07-18 17:38:27 +0000 This was was cloned from bug 17161 as part of operation convergence. Originally filed: 2012-05-23 13:49:00 +0000 ================================================================================ #0 contributor@whatwg.org 2012-05-23 13:49:49 +0000 -------------------------------------------------------------------------------- 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 ================================================================================ #1 Boris Zbarsky 2012-05-23 13:50:43 +0000 -------------------------------------------------------------------------------- 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. ================================================================================ #2 Philip J 2012-05-23 14:50:56 +0000 -------------------------------------------------------------------------------- Opera supports elm.properties("foo") as per spec, but I don't object to dropping it. ================================================================================ #3 Philip J 2012-05-23 14:51:32 +0000 -------------------------------------------------------------------------------- Discussion spawned from https://bugzilla.mozilla.org/show_bug.cgi?id=591467 ================================================================================ #4 David Zbarsky 2012-05-25 00:25:57 +0000 -------------------------------------------------------------------------------- Also, PropertyNodeList doesn't need legacycaller, since NodeList no longer has legacycaller. ================================================================================ 72242 1 Ms2ger 2012-08-15 17:13:42 +0000 Filter on [Idon'tcareaboutHTMLWGbugspam]. 74194 2 silviapfeiffer1 2012-09-21 10:22:00 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the Editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the Tracker Issue; or you may create a Tracker Issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Accepted Change Description: Patch applied https://github.com/w3c/html/commit/fca0a2c9df9f5524162aefada6c856a8d81d62e0 Rationale: adopted from WHATWG