HTMLOptionsCollection remove() argument should be long, not unsigned long

LayoutTests/fast/js/resources/select-options-remove.js

Index: LayoutTests/fast/js/resources/select-options-remove.js
diff --git a/LayoutTests/fast/js/resources/select-options-remove.js b/LayoutTests/fast/js/resources/select-options-remove.js
index 61c0d7c187d1aaff07a034da7b9f4ced45b33af3..b64b60577adc758b9d26d16c3145c2e28387b81d 100644
--- a/LayoutTests/fast/js/resources/select-options-remove.js
+++ b/LayoutTests/fast/js/resources/select-options-remove.js
@@ -240,3 +240,27 @@ shouldNotBe("select2.parentNode", "null");
 shouldBe("select2.remove()", "undefined");
 shouldBeNull("select2.parentNode");
 debug("");
+
+debug("2.18 Remove index -2147483649 from non-empty Options");
+shouldBe("select2.options.remove(-2147483649)", "undefined");

[philipj_slow, 2015/06/29 09:33:05]

Checking the return value of remove() doesn't seem meaningful, as it's always
void.

Is it possible to write a test that would fail with the old code and pass with
the new? It seems to me that there isn't, because we can only test with a small
number of options (certainly less than two billion) and the difference is only
observable around INT_MAX and INT_MIN. Can you confirm?

[shiva.jm, 2015/06/30 05:33:23]

Done.

+debug("");
+
+debug("2.19 Remove index -2147483648 from non-empty Options");
+shouldBe("select2.options.remove(-2147483648)", "undefined");
+debug("");
+
+debug("2.20 Remove index -2147483647 from non-empty Options");
+shouldBe("select2.options.remove(-2147483647)", "undefined");
+debug("");
+
+debug("2.21 Remove index 2147483649 from non-empty Options");
+shouldBe("select2.options.remove(2147483649)", "undefined");
+debug("");
+
+debug("2.22 Remove index 2147483648 from non-empty Options");
+shouldBe("select2.options.remove(2147483648)", "undefined");
+debug("");
+
+debug("2.23 Remove index 2147483647 from non-empty Options");
+shouldBe("select2.options.remove(2147483647)", "undefined");
+debug("");