[Bug 8037] The form controls collection should just be an HTMLCollection instead of having an HTMLFormControlsCollection interface

http://www.w3.org/Bugs/Public/show_bug.cgi?id=8037


Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED




--- Comment #2 from Ian 'Hixie' Hickson <ian@hixie.ch>  2009-10-25 06:01:35 ---
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: Partially Accepted
Change Description: see diff given below
Rationale: Done, except I made HTMLFormControlsCollection be its own interface
and put namedItem() on both interfaces so HTMLFormControlsCollection's
namedItem() overrides HTMLCollection's. I think we will probably need to add
more members to HTMLFormControlsCollection in time, because IIRC IE implements
form.elements as just an alias for form, and thus there are probably pages
depending on form.elements.foo where foo is something on HTMLFormElement (the
same problem we have with HTMLOptionsCollection).


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Sunday, 25 October 2009 06:01:39 UTC