jQuery UI tips and tricks

[davydotcom]

jQuery UI tips and tricks

[dhh]

How is the datepicker currently initialized? Using jQuery.ready?

[davydotcom]

No, it just runs. and sets initialized = false;

If initialized = false it recreates the date picker div. If initialized = true, .datepicker() on an object will not create the div.

It's kinda lazy initialized.

On Oct 5, 2012, at 9:56 AM, David Heinemeier Hansson [email protected] wrote:

How is the datepicker currently initialized? Using jQuery.ready?

—
Reply to this email directly or view it on GitHub.

[davydotcom]

Also,
I looked into firing document.ready() as an event for jQuery, but unfortunately jQuery removes the events from the event listener as they are fired from the ready event. So there is no way to re-fire those events.

On Oct 5, 2012, at 9:56 AM, David Heinemeier Hansson [email protected] wrote:

How is the datepicker currently initialized? Using jQuery.ready?

—
Reply to this email directly or view it on GitHub.

[ryanflorence]

The jQuery datepicker initializes on the first call to $.fn.datepicker, and then sets a global variable to true.

https://github.com/jquery/jquery-ui/blob/master/ui/jquery.ui.datepicker.js#L1816-1820

@davydotcom's solution will bind the mousedown event with every page load, which is terrible.

You just need to append the element to the document again:

jQuery.datepicker.dpDiv.appendTo( jQuery('body') );

... or open tickets with jQuery UI (and everybody else in the world) to jump hoops to decide if their widgets have been blown away or not :P

[davydotcom]

Ah, thanks

On Oct 18, 2012, at 10:52 PM, Ryan Florence [email protected] wrote:

... or open tickets with jQuery UI (and everybody else in the world) to jump hoops to decide if their widgets have been blown away or not :P

[davydotcom]

Actually there is already a ticket and pull request for the date picker to fix this bug anyway. The bug is the fact that if the dpDiv does not exist in the body, to readd it.

This affects more than just turbolinks, it apparently affects some other edge cases as well.

On Oct 19, 2012, at 8:05 AM, [email protected] wrote:

Ah, thanks

On Oct 18, 2012, at 10:52 PM, Ryan Florence [email protected] wrote:

... or open tickets with jQuery UI (and everybody else in the world) to jump hoops to decide if their widgets have been blown away or not :P

[ryanflorence]

@davydotcom, nice, they have a pull request open too:

Bug tracker

http://bugs.jqueryui.com/ticket/5679

pull request

jquery/jquery-ui#543

[rafalbromirski]

I know that this ticket is closed but I solved this problem in different way:

$(document).on 'page:change', ->
  $.datepicker.initialized = false

It works like a charm.

[davydotcom]

This was originally mentioned in the issue, however it causes the date
picker to add multiple event listeners

On Wednesday, December 19, 2012, Rafal wrote:

I know that this ticket is closed but I solved this problem in different
way:

$(document).on 'page:change', ->
$.datepicker.initialized = false

It works like a charm.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/76#issuecomment-11527748.