Dispatch change event for input type=color when colorpicker is closed

LayoutTests/fast/forms/color/input-color-choose-default-value-after-set-value.html

Index: LayoutTests/fast/forms/color/input-color-choose-default-value-after-set-value.html
diff --git a/LayoutTests/fast/forms/color/input-color-choose-default-value-after-set-value.html b/LayoutTests/fast/forms/color/input-color-choose-default-value-after-set-value.html
index 71a0f1d91e64507a831eb3ef1b5a96e14dd4a917..dbe78a0863055b21a408bb266dbded239256c0eb 100644
--- a/LayoutTests/fast/forms/color/input-color-choose-default-value-after-set-value.html
+++ b/LayoutTests/fast/forms/color/input-color-choose-default-value-after-set-value.html
@@ -21,6 +21,7 @@ clickElement(input);
 input.value = '#ff0000';
 shouldBe('input.value', '"#ff0000"');
 internals.selectColorInColorChooser(input, '#ffffff');
+internals.endColorChooser(input);

[keishi, 2014/09/17 08:15:54]

I don't think we need to add this. The input.value should change right after the
user selects a a color in the color chooser and so we should be testing that.

[Habib Virji, 2014/09/17 08:30:42]

Actually, line 17 above is printed in the test, as it is also testing change
event generated. Should I remove change event generation?

[keishi, 2014/09/18 03:50:55]

You're right, this test is about change event generation so we shouldn't remove
it. This line should go after line 25.

[Habib Virji, 2014/09/18 12:42:05]

I will but then expected files will need to be changed too, as previously when
selectColorInColorChooser is called, it generated change event and then color
input value was checked. As per your suggested change, it will be first input
value and then change event,

 shouldBe('input.value', '"#ffffff"');
 </script>
 </body>