12861 2011-06-02 22:13:58 +0000 HTMLOptionsCollection.add(wrongElementType) should throw 2011-08-12 23:20:22 +0000 1 1 1 Unclassified HTML WG LC1 HTML5 spec unspecified All All RESOLVED FIXED P2 normal --- 1 cam ian brunoaiss ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 49082 0 cam 2011-06-02 22:13:58 +0000 The spec currently says that if HTMLOptionsCollection.add() is passed something that isn't an HTMLOptionElement or HTMLOptGroupElement that the method does nothing. All browsers seems to throw, instead: http://people.mozilla.org/~cmccormack/tests/options-collection-add.html 49770 1 brunoaiss 2011-06-17 07:57:28 +0000 And it seems like throwing an exception makes more sense... That way, debugging javascript code will be easier. 53304 2 mike 2011-08-04 05:12:32 +0000 mass-move component to LC1 54837 3 ian 2011-08-12 23:19:55 +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: see diff given below Rationale: Concurred with reporter's comments. Fixed it with a WebIDL change. Note: I didn't test the second argument to see if it is type-checked also. 54838 4 contributor 2011-08-12 23:20:22 +0000 Checked in as WHATWG revision r6440. Check-in comment: closer to existing implementations http://html5.org/tools/web-apps-tracker?from=6439&to=6440