W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > October 2009

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

From: <bugzilla@wiggum.w3.org>
Date: Fri, 23 Oct 2009 22:45:40 +0000
To: public-html-bugzilla@w3.org
Message-ID: <bug-8037-2486@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8037

           Summary: The form controls collection should just be an
                    HTMLCollection instead of having an
                    HTMLFormControlsCollection interface
           Product: HTML WG
           Version: unspecified
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML5 spec bugs
        AssignedTo: dave.null@w3.org
        ReportedBy: mjs@apple.com
         QAContact: public-html-bugzilla@w3.org
                CC: ian@hixie.ch, mike@w3.org, public-html@w3.org


In browsers that expose global interface objects, the form control collections
either are or inherit from HTMLCollection, thus allowing changes to
HTMLCollection.prototype to affect them. In HTML5, it does not inherit, so it
will not be affected by HTMLCollection.prototype changes. This seems like a
needless change in behavior.

If HTMLCollection.namedItem is changed to return "object" instead of "Element"
as suggested in related bugs, then having a special interface for form control
collections will add very little value (just making the return type of the
"item" method a little more specific). Thus, I don't think it's worthwhile
having a special interface for it at all. But at the very least it should
inherit.


-- 
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 Friday, 23 October 2009 22:45:44 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 23 October 2009 22:45:45 GMT