From 5ab4b615a52e1b826d4db37a2174d2abca7056ac Mon Sep 17 00:00:00 2001 From: Richard Worth Date: Thu, 31 Dec 2009 01:11:23 +0000 Subject: [PATCH] Datepicker: added visual test page for #4071 --- .../datepicker/datepicker_ticket_4071.html | 95 +++++++++++++++++++ 1 file changed, 95 insertions(+) create mode 100644 tests/visual/datepicker/datepicker_ticket_4071.html diff --git a/tests/visual/datepicker/datepicker_ticket_4071.html b/tests/visual/datepicker/datepicker_ticket_4071.html new file mode 100644 index 000000000..ede987bc7 --- /dev/null +++ b/tests/visual/datepicker/datepicker_ticket_4071.html @@ -0,0 +1,95 @@ + + + + Datepicker Visual Test : Datepicker ticket #4071 + + + + + + + + + + + +

#4071 - 'length' is null or not an object

+ +

Summary

+In Internet Explorer, when a event such as click on one element causes a change event on another element to trigger programmatically, any change event handler that was bound to that second element through onchange gets the click event instead of the change event. + +

Steps to reproduce

+

+To demonstrate the issue, do one of the following: +

+ +

+Each will trigger change on the text input. The input has a handler bound in three different ways. Notice the difference when pressing a number in the input and bluring versus either selecting a date or pressing one of the first three buttons. In Internet Explorer, when the issue is present, 2 out of the three event objects are of type 'click' instead of 'change' and have the wrong corresponding srcElement/target when the datepicker or one of the first three buttons are clicked. +

+ + + + + + + + +