10990 2010-10-07 21:51:53 +0000 HTMLFormElement.namedItem missing a case 2011-08-04 05:05:44 +0000 1 1 1 Unclassified HTML WG LC1 HTML5 spec unspecified All All RESOLVED FIXED P2 normal --- 1 cam ian ian mike mounir public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 40820 0 cam 2010-10-07 21:51:53 +0000 Step 2 of the algorithm for HTMLFormElement.namedItem currently says: Otherwise, name is the name of one of the entries in the form element's past names map: return the object associated with name in that map. However, it is possible to call namedItem with a name that is neither an element currently in the form nor the name of one of the entries in the past names map, since you can call namedItem directly: var f = document.createElement('form'); f.namedItem('abc'); The algorithm should handle this case, or you should change the name getter declaration to: omittable caller getter any namedItem(in DOMString name); so that there is no namedItem property on HTMLFormElements, if that's the intention. (This may apply to other interfaces with name getters; I didn't check.) 41310 1 ian 2010-10-14 08:25:02 +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: Partially Accepted Change Description: see diff given below Rationale: I just removed the names altogether, there's no use case for having them. The compat need is just for the indexing and calling abilities, IIRC. (I was unfortunately unable to test IE to check this. Please reopen the bug if this is a compat regression, and I'll fix it the other way instead.) 41311 2 contributor 2010-10-14 08:26:50 +0000 Checked in as WHATWG revision r5624. Check-in comment: remove form.item() and form.namedItem() since 2/3 browsers I tested don't have it and removing them seems like a win. http://html5.org/tools/web-apps-tracker?from=5623&to=5624 41385 3 923 cam 2010-10-14 21:59:22 +0000 Created attachment 923 Test whether HTMLFormElement name getter works This test alerts an HTMLInputElement in IE9b. 52974 4 mike 2011-08-04 05:05:44 +0000 mass-moved component to LC1 923 2010-10-14 21:59:22 +0000 2010-10-14 21:59:22 +0000 Test whether HTMLFormElement name getter works form-nameditem.html text/html 94 cam PCFET0NUWVBFIGh0bWw+Cjxmb3JtPjxpbnB1dCBuYW1lPWFiYz48L2Zvcm0+CjxzY3JpcHQ+CmFs ZXJ0KGRvY3VtZW50LmZvcm1zWzBdLmFiYykKPC9zY3JpcHQ+Cg==