Search and Top Navigation
#6935 closed bug (duplicate)
Opened February 03, 2011 06:08PM UTC
Closed March 01, 2012 12:41PM UTC
Last modified March 01, 2012 12:46PM UTC
Datepicker create event not being executed like other events.
Reported by: | delwyn | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | 1.9.0 |
Component: | ui.datepicker | Version: | 1.8.9 |
Keywords: | Cc: | ||
Blocked by: | Blocking: |
Description
Hi
The Datepicker does not seem to execute the create event as specified in the demo:
$( ".selector" ).datepicker({
create: function(event, ui) { ... }
});
It works with all other events listed there.
Thanks
Attachments (0)
Change History (9)
Changed February 16, 2011 01:49PM UTC by comment:1
Changed February 16, 2011 01:52PM UTC by comment:2
status: | new → open |
---|
Replying to [comment:1 suner]:
I think I see the same issue using jQuery 1.4.4 and jQueryUI 1.7.3.
The create event didn't exist in any widget in 1.7.3.
Changed March 02, 2011 11:16AM UTC by comment:3
Nope, I see this exact same behavior as well. Using jquery 1.5.1 and jquery-ui 1.8.10.
Changed March 02, 2011 11:33AM UTC by comment:4
This is easy to reproduce:
1) Go to http://jqueryui.com/demos/datepicker/
2) enter the following into firebug:
$('#datepicker').datepicker("destroy");
$('#datepicker').datepicker({
create: function(a,b) {
console.log("create");
},
onSelect: function(a,b) {
console.log("onSelect");
},
onClose: function(a,b) {
console.log("onClose");
}
});
"create" never gets logged.
Changed December 02, 2011 11:20PM UTC by comment:5
I'm experiencing the same issue; here I was able to reproduce it using jQuery 1.7.1 and jQueryUI 1.8.16:
Changed March 01, 2012 12:39PM UTC by comment:6
_comment0: | Still existing in 1.8.18. Why on earth is this not fixed yet? → 1330605923653523 |
---|
Still existing in 1.8.18. Why on earth is this not fixed yet? Either fix it or remove it from documentation!
Changed March 01, 2012 12:41PM UTC by comment:7
resolution: | → duplicate |
---|---|
status: | open → closed |
Changed March 01, 2012 12:46PM UTC by comment:9
Ah I see; won't hold my breath then ;)
I think I see the same issue using jQuery 1.4.4 and jQueryUI 1.7.3.