20720 2013-01-21 05:55:53 +0000 Define HTMLSelectElement.remove() (without argument) to do the same as ChildNode.remove() 2013-09-30 18:12:35 +0000 1 1 1 Unclassified WHATWG HTML unspecified PC All RESOLVED FIXED P2 normal Unsorted 23398 1 killxxxvi ian bzbarsky cam erik.arvidsson ian killxxxvi mike Ms2ger syoichi www-dom contributor oldest_to_newest 81619 0 killxxxvi 2013-01-21 05:55:53 +0000 The remove() method from Interface Element [ http://www.w3.org/TR/dom/#dom-childnode-remove ] is overwritten with The remove() method from Interface HTMLSelectElement [ http://www.w3.org/TR/REC-DOM-Level-1/level-one-html.html#ID-33404570 ] for the select nodes. Today, I have to use something like this: window.HTMLSelectElement && function(HTMLSelectElementPrototype) { var removeOption = HTMLSelectElementPrototype.remove; HTMLSelectElementPrototype.remove = function() { if (arguments[0] >= 0) removeOption.call(this, arguments[0]); else this.parentNode && this.parentNode.removeChild(this); }; }(window.HTMLSelectElement.prototype); It would be better to change HTMLSelectElement Interface so that without arguments it used remove method like Element Interface. 81620 1 Ms2ger 2013-01-21 07:48:12 +0000 Hrm, <http://www.whatwg.org/html/#the-select-element> has void remove(long index); so I guess we could make it work with our void remove(); but I'm not sure if WebIDL supports that... Cameron? 81639 2 bzbarsky 2013-01-21 13:39:56 +0000 One option would be for HTMLSelectElement to define overloads with and without and index and explicitly say that the no-argument overload does the same thing as the canonical Element.prototype.remove. That's how an ES implementation would have to implement it, and I think specifying it that way is simplest. It also happens to be simple to implement, at least in Gecko. ;) 81640 3 annevk 2013-01-21 13:59:54 +0000 Ian, care to make that change in HTML? 81906 4 cam 2013-01-21 22:47:00 +0000 I agree with Boris; that's the simplest solution. (I think overloading operations with those from an inherited interface could be confusing for the reader.) 81962 5 killxxxvi 2013-01-22 19:24:12 +0000 Hi guys! I was wondering what is the difference between selectNode.remove(optionIndex) and selectNode[optionIndex].remove()? Do we need 2 different methods for doing extactly the same thing? Maybe this situation occurred because the method "remove" from HTMLSelectElement interface was so replaceable and too few people really enjoyed them? Maybe it is time for him to retire? 81963 6 Ms2ger 2013-01-22 19:26:09 +0000 HTMLSelectElement.remove(i) removes the i'th option element from the this element; ChildNode.remove() removes the this object from its parent, if any. 81965 7 killxxxvi 2013-01-22 19:40:41 +0000 HTMLSelectElement.remove(i) - removes the i'th option HTMLSelectElement[i].remove() - removes the i'th option it is 100% replaceable, am I right? 81966 8 Ms2ger 2013-01-22 19:41:54 +0000 Sure. We can't remove select.remove(i), though, because pages use that. 81967 9 killxxxvi 2013-01-22 19:47:02 +0000 Is a pity, it would be a little easier. 82113 10 ian 2013-01-24 23:24:08 +0000 Having remove() remove the element from its parent and remove(i) remove a child from the element is very confusing. Can't we rename ChildNode.remove()? 82130 11 syoichi 2013-01-25 03:54:34 +0000 WebKit already implemented ChildNode.remove() by Erik Arvidsson, and Google Chrome 24(stable) has it now. http://wkrev.com/129400 http://wkb.ug/73885 But I guess that web developers aren't so using ChildNode.remove()... 82138 12 Ms2ger 2013-01-25 13:13:49 +0000 Do you have a better name? 82166 13 ian 2013-01-25 22:36:12 +0000 unparent() removeFromParent() detach() 84748 14 ian 2013-03-20 18:56:01 +0000 I'm kicking this over to DOM, because remove() on HTMLSelectElement is ancient and having both do basically opposite things is going to be very confusing. 84774 15 annevk 2013-03-21 14:46:10 +0000 It does not seem that confusing to me that on one element there is an overloaded version that removes a child via an index which is largely a legacy API anyway. 87236 16 ian 2013-05-04 06:41:24 +0000 How is a method that does two diametrically opposite things not confusing?? 93333 17 annevk 2013-09-13 07:57:51 +0000 So I don't think we're going to change. Hmm. 93667 18 Ms2ger 2013-09-23 19:24:32 +0000 Firefox 23 ships this. 93668 19 contributor 2013-09-23 19:31:43 +0000 Checked in as WHATWG revision r8192. Check-in comment: remove() is also defined on an ancestor interface, so overload it here on <select>. http://html5.org/tools/web-apps-tracker?from=8191&to=8192